Owning surface
Run detail and Mission ReplayStart where the product already explains or controls the problem.
Support
Run failed
A failed run means the runtime hit a blocking condition it could not safely recover from on its own.
Guide summary
Use this page to understand the surface before you act inside it.
Understand what a failed run means, where to inspect it, and when to continue, retry, or report it.
Guide type
SupportThis guide reflects the current product workflow and surface ownership.
Sections
5Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Escalation rule
Use support with contextAttach the relevant run, mission, task, or artifact whenever possible.
Related action
Contact Support only after inspectionSupport is strongest when the dominant symptom is already known.
Guide section
Symptoms
These signals usually indicate this specific class of problem.
What it is
Understand what a failed run means, where to inspect it, and when to continue, retry, or report it.
When to use it
Use this guide when these symptoms match what you see in the product.
Where to find it
Start from the owning surface: Run detail and Mission Replay.
What happens next
You narrow the problem before you retry or escalate.
Common mistake
Escalating too early without checking whether the owning surface already explains the blocker.
Related action
Open the owning surface first, then return here if the diagnosis is still unclear.
- Run status shows failed
- A failed step appears in run detail
- No artifact or only partial output is available
Guide section
Likely causes
- Provider execution failed
- Review or approval conditions blocked the run
- A specific step hit a runtime or context problem
- The run depended on missing or invalid inputs
Guide section
How to fix it
- Open the run detail page and inspect the failed step
- Use Mission Replay to identify the real blocking moment
- Use Continue Run if the UI shows a safe resume path
- Use Retry Failed Step only after the underlying issue is fixed
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Run detail and Mission Replay
What happens next
The owning surface should tell you whether the next move is fix, retry, continue, or support.
Related action
Move into Run detail and Mission Replay now if you have not already done so.
Guide section
When to contact support
Use Report this Run if the failure still does not make sense after Replay and step inspection.
Tip
Report with the right object
A linked run or artifact is much easier to investigate than a generic support request with no runtime context.