Job states

States

State	Meaning	Terminal
booked	Accepted, with a node and a start time assigned
queued	Waiting for capacity. No slot yet
running	The container is up and spending tokens
finished	Ran to completion, or the runtime expired	✓
failed	Stopped by an error - usually the image or the command	✓
canceled	Stopped by a user or an administrator	✓

Service rows can also show transitional detail such as downloading image while the node pulls it.

Transitions

            ┌──────────► queued ──┐   (no capacity yet)
submit ─────┤                     ├──► running ──┬──► finished
            └──────────► booked ──┘              ├──► failed
                                                 └──► canceled

• booked → running when the start time arrives and the image is pulled.
• queued → booked when capacity frees up.
• running → finished when the command exits or the runtime expires.
• any non-terminal → canceled when someone cancels it.

Nothing leaves a terminal state. A second run is a new job, which is what Clone, Requeue and Restart produce.

What each state allows

	Terminal	Logs	Extend	Cancel	Edit	Restart	Clone
booked				✓	✓		✓
queued				✓	✓		✓
running	✓	✓	✓	✓	✓	✓	✓
finished		✓					✓
failed		✓		✓*	✓	✓*	✓
canceled		✓					✓

* An interactive job that fails keeps its resources on the node until its time is up, so it can be fixed and restarted in place. Cancel it to release them; after that it can only be cloned. A failed batch job releases its resources at once and can only be cloned.

How a job reports its services

A job holding several services summarises rather than picking one: the row says how many are running. Expand it to see each service’s own state.

Common causes of failed

Cause	Tell
Image does not exist	manifest unknown in the logs
Private image, no registry selected	pull access denied
Command exits non-zero	The command’s own error
Out of memory	Killed shortly after start under load