Skip to content

Runs and readback

Runs retain execution state and version evidence so you can distinguish launch, progress, completion, and repair.

Runs are execution records in Agents & Workflows. Readback shows the saved version, current state, and retained result for one attempt at work.

Ownership

A Workflow Run belongs to the template version used at launch. An Agent editor Run uses a saved Agent in a one-block Workflow. The start result records the Agent version and configuration fingerprint. The Run records which member started it. The Agent's own identity controls what may run. Open /workflows/runs/[runId] in the Console for its timeline and local detail.

States

A Run in running is still executing. paused holds progress, and needs_attention calls for inspection. cancelling is still settling the stop request. The terminal states completed, cancelled, and failed end the Workflow Run. A completed block is only part of the Run's progress. Do not infer success from a launch response or a count of finished blocks.

Boundaries

A Run summary is a readback of execution, not the definition that authorized it. The Agent trace retains lifecycle events from which its summary can be rebuilt. Task history records changes to one assignment. Activity follows executions across kinds and points back to their owners. Neither view replaces the Run's local result when you must decide whether a specific effect finished.

Failures

A Run can fail even when its definition saved and launch succeeded. Read its error and the affected block before choosing recovery. A missing summary can also be a readback fault: the Agent trace may still exist. Losing the browser's observation does not cancel the Run. The editor's stop-observation control ends polling. The retained execution may continue.

Recovery

A Run must be read again before a control action. Resume requires paused. Block retry requires a failed block in a nonterminal Run. A terminal Run cannot be resumed or retried in place. The internal repair service can rebuild a missing Agent summary from its trace without rerunning effects. Use the summary contract for the supported read and Reviews and repair for state-specific recovery.