Run states, and why a run failed
Queued, running, then exactly one of finished, failed or stopped. A failed run says why.
Updated 1 min read
| State | What it means |
|---|---|
| Queued | Accepted, not started yet. The run page says why it is waiting, its place in line and, when known, when it should start. |
| Running | Working. Its transcript grows as it goes. |
| Finished | It reached a result. |
| Failed | It ended without a result. The reason is shown, for example deadline exceeded, or the sandbox exiting without a result. |
| Stopped | A person, a key or a kill switch stopped it. |
A run that has ended stays ended: it cannot be restarted. Start a new one.
Common reasons a run failed
- Deadline exceeded: the task needed longer than its deadline. Give a longer deadline, or split the task.
- Turn limit: it used every turn before finishing. Raise Most turns, or make the task narrower.
- The spend ceiling: the account reached its daily model spend ceiling; see The daily spend ceiling.
- The sandbox exited without a result: something inside the sandbox stopped. Start the run again; if it repeats, write to us with the run’s id.