A run is always in exactly one state. The state appears as a label at the top of the run detail page. This page is the exhaustive list; for a walk-through of how the states fit together, see the Run states concept page.
There are nine states: one active, five that wait on you, and three that end the run.
Every state
| State | What it means | Entered when | Your action |
|---|---|---|---|
| Running | Working — planning, coding, or moving through the pipeline. | The run starts, or resumes from a waiting state. | None. You may pause it (while Developing) or cancel it. |
| Awaiting Plan Approval | A plan is ready for your decision, before any code is written. | A plan finishes generating. | Approve or reject the plan. |
| Waiting for Gate | Held at a stage’s gate until its condition is met. | A stage opens a pull request, its E2E tests are pending, or a deploy is awaited. | Satisfy the gate — merge the pull request, or run the E2E tests. |
| Waiting for Answer | The run asked a question it can’t decide on its own. | The run hits an ambiguity it needs resolved. | Answer the question on the run detail page. |
| Waiting for Payment | Paused because the organization’s balance ran out mid-task. | The balance reaches zero mid-run. | Top up the balance; the run resumes. |
| Paused | The run is on hold at a temporary, resumable checkpoint. | You select Pause while it’s Developing, or the run reaches a hold point and parks itself. | Select Resume on the run or task detail page. |
| Completed | The run finished the whole pipeline successfully. | The last stage clears. | None — a finished record. |
| Failed | The run hit an error it couldn’t recover from. | A step errors, or a stage gate fails. | Start a new run to try again. |
| Cancelled | The run was stopped deliberately. | You cancel the run, or reject its plan. | Start a new run if you still want the task done. |
Transitions
- Running moves to any of the five waiting states when it needs something from you, or to Completed, Failed, or Cancelled when it ends.
- Each waiting state returns to Running the moment you provide what it asked for — except Awaiting Plan Approval, which goes to Running if you approve and to Cancelled if you reject.
- Running moves to Paused when you select Pause — the run finishes its current step (showing Pausing… until it does), then parks. While paused, the project stays busy with the run.
- Paused returns to Running when you select Resume, continuing from the step after the pause — completed work is never repeated. If the run can’t continue yet, it parks again as Paused — select Resume once more shortly after.
- Waiting for Payment resumes at the step after the one where it paused — completed work is never repeated.
- Completed, Failed, and Cancelled are final. A run that reaches one never moves again. The task itself isn’t finished — you can start a fresh run.
What “Running” shows
While a run is Running, the label often refines to the activity in progress, so you can follow along: Planning, Developing, Reviewing, Unit testing, E2E testing, syncing docs, Versioning. These are display detail, not separate states — the run is still Running throughout.
Waiting states never time out
A run in any of the five waiting states holds its place indefinitely. It won’t expire, move on, or fail on its own — it waits until you act. Take the time you need.