Diagnose a failed run

Every failed run can be attested with a confirmed cause. Attestation builds the failure record your team uses to fix agents, and some workflows require it before they run again.

Attest a cause

1. 1Go to Flagged Reviews > Failures, or select Failures pending attestation on Active Work.
2. 2Open the failed run. Review the failed step, the reason, and the side-by-side diff.
3. 3If AMC shows an AI-suggested cause, select Accept, Edit, or Reject. Otherwise select Confirm cause.
4. 4Pick a cause from the taxonomy. If you pick Other, notes are required.
5. 5Select Save attestation.

The confirmed cause shows who attested it, and View history shows earlier versions.

Compare with the golden run

When the workflow has a golden run, the Side-by-side diff lines up each step of the failed run against it and marks each one Matched, Diverged, Failed, Skipped, or Missing. With no golden run, promote a recent successful run first. See Set and retire golden runs.

Mark a run Failed or Complete

If a run's outcome is wrong, correct it. The run's status badge stays the same; its outcome changes, and ROI pass rates follow.

1. 1Open the run.
2. 2Select Mark Failed (on a completed run, or one waiting on a person) or Mark Complete (on a failed run).
3. 3Enter a Reason of 10 to 500 characters.
4. 4Confirm. The change is recorded under Governance > Completion Overrides and in the audit log.

Failure causes come from a core taxonomy managed centrally. A Tenant Admin can turn on AI cause suggestions under Settings > Failure Causes > AI suggestions by entering a Foundry project endpoint and model.