Owning surface
Run detail, Mission Replay, and contextual Report this Run entryStart where the product already explains or controls the problem.
Support
Run stuck or queue still processing
A run that looks stuck is not always broken, but it does need the right kind of inspection.
Guide summary
Use this page to understand the surface before you act inside it.
Recover when a run appears to be queued or processing longer than expected.
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
Recover when a run appears to be queued or processing longer than expected.
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, Mission Replay, and contextual Report this Run entry.
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 stays queued or processing
- Mission Orb stays in a processing posture for too long
- No new artifact or replay movement appears
Guide section
Likely causes
- Background execution is still in progress
- The queue or runtime has not advanced yet
- The run is waiting on a blocked step or provider response
- A recoverable issue stopped forward motion without finalizing the run
Guide section
How to fix it
- Wait briefly if the runtime is actively moving
- Refresh run detail and Mission Replay
- Use Continue Run if the UI exposes it as the safe fallback path
- Report the run if the posture remains unchanged and no explanation appears
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Run detail, Mission Replay, and contextual Report this Run entry
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, Mission Replay, and contextual Report this Run entry now if you have not already done so.
Guide section
When to contact support
Contact support when the run remains unchanged and the runtime gives no useful explanation.
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.