Skip to main content
For a check managed in Checkly, automatic repair can attempt to fix a Browser or Multistep Check when its script fails because of a check issue. A check intent states the goal, required outcomes, and guardrails that a repair must preserve. A failed check is not automatically repaired just because this setting is on; Rocky AI first needs a repairable failure and a valid intent. Browser and Multistep Checks linked to a GitHub source file can also receive a repair proposal through a pull request. Merge and deploy that change to update the running check.
  • A saved Browser or Multistep Check
  • Permission to edit the check
  • Rocky AI enabled for automatic root cause analysis, with AI invocations available for analysis and repair

​
Enable automatic repair

  1. Open the check editor and expand Automatic Repair in the check settings.
  2. Review the Check intent. It needs a goal and at least one required outcome or guardrail. Include the outcomes the check must still prove, such as a successful sign-in or an order confirmation. Add guardrails for behavior a repair must not weaken, such as authentication.
  3. Under Automatic repair behavior, select On to enable repair for this check. You can also select Account default to follow the account setting.
  4. Save the check.
An AI-generated check already has an intent. Review it before enabling repair. Repair cannot start without a valid intent, even if the check or account setting is on.

​
Add intent to an existing check

For an existing Browser or Multistep Check, select Initialize from saved check in the Check intent section. Checkly reads the saved script and dependencies and suggests an intent. Review the suggestion, edit its goal and outcomes if needed, then save the check. The suggestion is not saved and repair is not enabled just by selecting the button. You can also write the intent yourself. Use this option when the script does not express all of the business requirements a repair must preserve. For example, a script might check that a page loads while the actual goal also requires a signed-in user to see the correct account.

​
Define intent with Monitoring as Code

You can also define intent in your Monitoring as Code configuration using the Checkly CLI. Keep the goal, required outcomes, and guardrails alongside your check definition. See the General Check Options in the Browser Check and Multistep Check construct references for the intent schema and a complete configuration example. Use your existing Browser or Multistep Check test file in these examples.
Defining intent does not by itself enable automatic repair or change which check types support Checkly-managed repair.

​
AI invocation usage

Root cause analysis and automatic repair each use one AI invocation from your plan’s allowance. Each AI Assistant conversation uses one invocation on its first run. Later messages in that conversation use no more invocations. Initialize from saved check does not use an invocation. See Rocky AI consumption and invocations.