Skip to content

Run States

A Run is always in one of five states, from the moment it is registered until it ends. The table below describes each state, plus the Warning indicator.

Run States Table

State Phase Typical action available What it means

Queued
Active Abort The Run is registered and waiting for the platform to start processing it.

Running
Active Abort The Run is being processed; counters update live.

Success
Terminal Rerun, Delete The Run finished cleanly. Summary metrics and result payload are authoritative.

Success + Warning indicator
Terminal Rerun, Delete A Success Run that recorded log entries during execution. Status stays Success; the warning icon only appears next to the Run ID to flag that the log is worth opening.

Failure
Terminal Resume (when supported), Rerun, Delete The Run stopped because of an unrecoverable error. Partial results are preserved; the operation log carries the root cause.

Aborted
Terminal Resume (when supported), Rerun, Delete A user (or the system) stopped the Run before completion. Partial results are preserved.

The Run row badge is text-only. The glyphs above appear on the operation detail page as the timeline step icon; on the Activity list, the only icon next to a Run ID is the warning indicator (when a Success Run produced logs). Queued and Running are shown in the UI as an animated spinner; the static loader icon in the table above represents both states.

Promote skips Queued

Promote is the one operation type that never shows the Queued state: it starts directly in Running. See Runs Lifecycle for its state diagram.

The actions are typical because their support varies by operation type; see the Runs Available Actions matrix for what each type supports. A Run cannot move out of a terminal outcome. Resume and Rerun create a brand-new Run rather than reopening the original; for how each transition happens, see Lifecycle.

See also