What do the run statuses queued, running, completed, failed and cancelled mean?
Every run has a status. Three of them are final.
| Status | Meaning | Final? |
|---|---|---|
queued | Accepted and waiting to start | No |
running | Cosmos is working | No |
completed | Finished; output holds the answer | Yes |
failed | Couldn't finish; error says why | Yes |
cancelled | Stopped with POST /v1/runs/{id}/cancel | Yes |
How a run moves#
queued ─▶ running ─▶ completed
├─▶ failed (error.code: run_failed | out_of_credits)
└─▶ cancelled
When you create a run, the API answers right away with the run, usually already running.
What to do with each#
- Not final yet: keep reading the event stream, or poll
GET /v1/runs/{id}no faster than every 2 seconds. - completed: read
outputandfiles. - failed: check
error.code.out_of_creditsmeans your balance ran out midway;run_failedcovers everything else. - cancelled: any files saved before the cancel are still listed.
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.