Failure Diagnosis Agent
When a workflow run fails, open the Failure Diagnosis agent to understand exactly what went wrong — and generate a corrected workflow you can save with one click.
Even deterministic workflows fail — a Slack channel gets renamed, a repo permission changes, an API field expects an ID where you gave it a name. When that happens, the usual loop is tedious: read the error, guess the cause, open the builder, change a parameter, re-run, and hope. Today we're collapsing that loop into one step with the Failure Diagnosis agent.
On any failed execution, open the agent to understand exactly what went wrong — and generate a corrected workflow you can save with one click.
Diagnosis where the failure happened
Open a failed run from the Executions page and the failed step is already marked on the DAG. From there, launch the Failure Diagnosis agent right alongside the execution. It has full context on the run — the trigger signal, every step's output, and the exact error — so it doesn't need you to paste logs or explain what the workflow was supposed to do.
Ask it anything about the failure:
- "Why did this workflow execution fail?"
- "What do I need to fix to make this workflow succeed?"
- "Is this a permissions issue or a configuration issue?"
From explanation to corrected workflow
The agent doesn't just explain the failure in plain English — it produces a corrected version of the workflow with the problem fixed. Review the proposed change, then save it with one click; the corrected definition opens in the builder so you can confirm everything looks right before reactivating. If the original workflow was deleted in the meantime, the agent offers to create a fresh workflow from the corrected version instead.
Pairs with replay
Failure diagnosis works hand-in-hand with execution replay. Once you've saved the corrected workflow, replay the failed run — from the beginning, or from the failed step to preserve the work the earlier steps already did. Together they turn a failed run into a fixed, re-run workflow in minutes, not a debugging session.
Getting Started
Open any failed execution under Workflows → Executions and launch Failure Diagnosis. It's available on every failed run, with no setup required.