Skip to main content
Available since CLI v7.8.0.
The checkly rca command lets you trigger and retrieve AI-powered root cause analyses (RCA) for error groups directly from the terminal. An RCA examines an error group and returns a classification, root cause explanation, user impact assessment, and suggested code fixes when available.
Before using checkly rca, ensure you have:
  • Checkly CLI installed
  • Valid Checkly account authentication (run npx checkly login if needed)
  • A Checkly plan that includes root cause analysis
For additional setup information, see CLI overview.
Existing root cause analysis results are also available via checkly checks get. Use checkly rca run to trigger a new analysis for an error group that doesn’t have one yet.

Usage

Terminal

Subcommands

SubcommandDescription
runTrigger a root cause analysis for a check or test session error group.
getRetrieve a root cause analysis by ID.

checkly rca run

Trigger a new root cause analysis for a check or test session error group. The analysis runs asynchronously — use --watch to wait for the result in your terminal. Usage:
Terminal
Options:
OptionRequiredDescription
--error-group, -eyes*The check error group ID to analyze.
--test-session-error-group, -teyes*The test session error group ID to analyze.
--user-context-Extra context to pass into the root cause analysis.
--watch, -w-Wait for the analysis to complete and display the result.
--output, -o-Output format: detail, json, or md. Default: detail.
*Pass either --error-group or --test-session-error-group.

Run Options

--error-group, -e
string
The check error group ID to trigger the analysis for. You can find error group IDs in the output of checkly checks get when viewing a check with errors.Usage:
Terminal
--test-session-error-group, -te
string
Available since CLI v8.0.0.
The test session error group ID to trigger the analysis for. You can find these IDs in the output of checkly test-sessions get.Usage:
Terminal
--user-context
string
Available in CLI v8.5.0+.
Extra context to pass into the root cause analysis. Use this to add details the error group does not contain, such as recent deploy changes or known service incidents.Usage:
Terminal
--watch, -w
boolean
default:"false"
Wait for the analysis to complete and display the full result. Without this flag, the command returns immediately with the RCA ID and a pending status.Only works with --output detail.Usage:
Terminal
--output, -o
string
default:"detail"
Set the output format. Use json for programmatic access or md for markdown.Usage:
Terminal

Run Examples

Terminal

checkly rca get

Retrieve an existing root cause analysis by its ID. If the analysis is still generating, use --watch to wait for completion. Usage:
Terminal
Arguments:
ArgumentDescription
idThe RCA ID to retrieve.
Options:
OptionRequiredDescription
--watch, -w-Wait for the analysis to complete if still generating.
--output, -o-Output format: detail, json, or md. Default: detail.

Get Options

--watch, -w
boolean
default:"false"
Wait for the analysis to complete if it is still generating. Without this flag, the command returns the current status immediately.Only works with --output detail.Usage:
Terminal
--output, -o
string
default:"detail"
Set the output format. Use json for programmatic access or md for markdown.Usage:
Terminal

Get Examples

Terminal

RCA Output

A completed root cause analysis includes:
  • Classification — the category of the error
  • Root cause — explanation of what caused the error
  • User impact — how the error affects end users
  • Code fix — suggested fix when available
  • Evidence — supporting artifacts from the analysis
  • Reference links — relevant external resources