Runs Lifecycle

Every Run progresses through a small set of states, from the moment it is queued until it reaches a terminal outcome. This page covers the state diagram, how Promote differs from the other operations, how per-container progress relates to the Run-level state, and where logs live.

State diagram

Every Run follows the same general lifecycle: an active phase (Queued, Running) followed by a terminal outcome (Success, Failure, or Aborted). Promote is the exception. It transitions directly to Running, skipping Queued.

flowchart LR
    Queued -->|processing starts| Running
    Queued -.->|user clicks Abort| Aborted
    Running -->|all containers processed| Success
    Running -.->|unrecoverable error| Failure
    Running -.->|user clicks Abort| Aborted

flowchart LR
    Running -->|all entities processed| Success
    Running -.->|unrecoverable error| Failure
    Running -.->|user clicks Abort| Aborted

Solid arrows: automatic transitions. Dotted arrows: user-initiated or error.

A Run cannot move out of a terminal outcome, but it can be re-launched with Resume or Rerun (see Available Actions). Each of those creates a brand-new Run rather than reopening the original.

Per-container progress vs Run-level state

Some operations (notably Profile and Scan) track progress at two layers:

1. Run-level state. The badge on the Activity row and the terminal outcome for the whole operation.
2. Container-level state. The per-container result inside the expanded Run, with its own Success/Failure badge.

These layers are independent. A container can land on Failure while the overall Run still finishes on Success. The failed container is recorded on the Run Results tab, and the Run-level Success carries the Warning indicator next to the Run ID. The container-level badge uses the same component and palette as the Run-level badge.

For Sync, External Scan, Export, Materialize, and Promote, all the work folds into a single Run-level state. There is no separate per-container badge.

Where logs live

Two log scopes are exposed for every Run:

• Run-level log. Surfaced in the expanded Run's Logs block and on the operation's detail page. Captures setup, scheduling, platform events, and any unrecoverable error.
• Container-level log. Surfaced alongside each container row inside the expanded Run, when the operation has a per-container progress layer (Profile, Scan). Captures the per-container query and any error that prevented the container from finishing.

While a Run is active, logs surface per container as each one finishes. The Run-level log arrives with the final result and does not change afterwards.

See also