The possible job states are: new, ready, running, stopping, stopped, finished, failed.
The transitions from new -> ready -> running usually happen very quickly. A job ultimately will have a status of one of these three: stopped, finished, failed.
State | Description
------------|------------------------------------------------------------
new | Job is recording the initial details
ready | Job is recorded but no nodes are running or queued
running | Job has nodes that are running or queued
stopping | Stop command issued but some nodes in job are still running
stopped | Job had stop command issued and is "completed"
finished | Job completed successfully on all nodes
failed | Job completed but some nodes had errors/failures
The console maps these strings in the Status column with these job state values from the Orchestrator API:
Console Status | api state
-----------------------|-----------
Queued | new, ready
In progress | running
Stopping | stopping
Succeeded | finished
Finished with failures | failed
Stopped | stopped