Run a root cause analysis

The Fix tab is Error Feed’s agentic root-cause chat thread, with a follow-up composer underneath it. Start it and sub-agents sample representative calls from the cluster, compare them against a passing baseline, and synthesise a written root cause and a proposed fix in the thread. This page walks through starting a run, reading what comes back, asking a follow-up, and re-running it later.

Run the analysis

Start from an issue’s detail page, with the failure pattern already confirmed via Investigate an issue.

From the issue’s detail page, click into the Fix tab. If nothing has run yet it shows an empty state, No analysis yet, with a button labeled Analyze this cluster. You can also start it from the issue’s headline card, whose button reads Debug this cluster before a run exists. Both start the same run, and each uses 1 credit, taken when the run starts and refunded if the run fails.

The Fix tab’s empty state, before any run has started

The run starts immediately and the tab keeps checking until it lands or fails, with a one-hour cut-off. The result arrives as a single written message in the thread: a root cause explaining what’s going wrong, and a proposed fix for it, based on the calls Falcon sampled. To probe the reasoning further, type into the composer at the bottom (placeholder: Ask Falcon a follow-up…), and Falcon is investigating… shows while a reply streams in.

Once the cluster has picked up new traces, click Re-run in the tab’s header (tooltip: Re-run with current cluster state (1 credit)) to analyze it against its current state. The headline card carries the same option once a run exists, tooltipped Re-run analysis (1 credit).

If it fails

A run can fail with one of two messages: Couldn’t start the analysis. Please try again. or Couldn’t connect to the server. Please try again. For what each one means and what to do about it, see Analysis doesn’t finish.

Dive deeper