Job statuses

reference · Reviewed 2026-07-30 GA

Every status a job or workstation reports in the list view and on the Status tab. For how these fit together, see the job lifecycle.

Job statuses

Status	Meaning
Draft	Saved but not yet submitted
Pending	Pending submission to the cloud provider
Queued	Preconditions such as capacity are being checked
Warning	A precondition produced a warning — for example, a budget threshold
Starting	The cluster is starting
Running	The job is executing
Completed	The job finished its task
Failed	The job failed due to an error
Stopping	The job is shutting down and saving files
Stopped	The job was manually stopped

Workstation statuses

Workstations report all of the above, plus three states that exist because a workstation can be paused instead of only terminated:

Status	Meaning
Active	The workstation is running and available to connect to
Suspending	The workstation is being paused; state is being preserved
Suspended	Paused — not billed for compute, resumable

List-view filters

The Jobs and Workstations page groups resources into filters that map onto these statuses:

Filter	Includes
Active	Pending, Queued, Starting, Running, Active
Completed	Completed, Failed, Stopped
Templates	Saved job configurations, not runs
Shared with Me	Resources another user shared with you
Archived	Resources you archived

Notes

• Completed is not a success assertion. It means the command ran and exited. Check the exit code and the solver output.
• Warning does not block a job. It's a precondition that passed with a caveat, most often a budget threshold crossing.
• Queued can be legitimate. Capacity checks take time; a queued job is not a stuck job.

Related

• The job lifecycle — how these statuses progress
• Exit codes — the process-level result
• Stop a job — moving a job out of a running state