Skip to main content

Get run status

GET 
/api/v1/runs/:run_id/status

Returns the current state of a run.

A terminal state is only reported with positive evidence. The status is resolved from the W&B run and then the Redis enqueue-time run-state record. SQS has no result backend. A run that neither store knows about is reported as unknown, which is never terminal. Absence is not failure: a run is invisible to W&B for the whole window between submission and the creation of its W&B run, queue wait included.

Normalised states are in-queue, running, unknown, finished, failed, crashed, killed, and lost. A run is terminal in every state except in-queue, running, and unknown.

lost now means one specific thing: a submitted run whose record never reached a terminal state and is older than the six-hour grace window. A queued or running record within that window remains non-terminal.

Do not resubmit on a non-terminal status. in-queue, running, and unknown all mean "keep polling". Resubmitting multiplies server-side runs of several hundred simulated respondents each.

Still true of finished: a run can finish having produced no artifacts. A W&B state of finished whose summary.status is failed is reported here as failed, but check logged_artifacts() before treating a finished run as usable.

Request​

Responses​

Successful Response