Run Statuses
Every run has a status: still live, blocked on something, finished, or recovering from an interruption. This page is the full list, with what each one usually asks of you.
Active statuses
| Status | What it means | What you usually do |
|---|---|---|
| Queued | Accepted but not started — usually a scheduled trigger waiting behind an active run. | Wait. |
| Running | The agent is generating, calling tools, working. | Watch, or let it finish. |
| Waiting | Blocked on other work — a delegated child run or a subrun. | Wait; open the linked child run if you're curious about the delay. |
| Paused | The agent needs something from you — an answer, an approval. | Read the pause reason and reply. |
| Finalizing | Wrapping up. Brief; you'll rarely catch it. | Nothing. |
The easy ones to confuse are Paused (needs you) and Waiting (needs other work to finish).
Terminal statuses
| Status | What it means | What you usually do |
|---|---|---|
| Completed | Finished normally with a final answer. | Continue the run to keep iterating, or start a new one. |
| Stopped | Manually stopped before finishing. | Continue it whenever — the context is intact. |
| Error | Failed: model issue, tool failure, permissions, balance... | Read the last output, fix the cause, continue or retry. |
| Max turns reached | Hit the agent's configured turn limit. | Continue the run, or raise the limit in Settings → Advanced if it keeps happening. |
Terminal never means lost. Any terminal run can be continued by sending another message.
Recovery statuses
After a service restart, node disconnect, or similar infrastructure hiccup, you may see a run marked Recovering after ... (shutdown, node disconnect, daemon restart), or the older generic Interrupted. These are not failures — Taurus is trying to resume the run and preserve the work. Usually you just wait; if an interrupted run doesn't come back on its own, continue it manually.
Related
- Runs — the broader run lifecycle
- Talking to Your Agent — run controls day to day