Workflow Run History

Info

Run History appears after a workflow has run. See the Visual Workflow Editor for the current workflow editor screenshot.

Workflow definitions and workflow runs are separate things.

A workflow definition is the editable graph: metadata, nodes, edges, variables, and input schema. It answers: what should run?

A workflow run is an execution record. It answers: what happened when the workflow ran?

What a Run Records

A workflow run can include:

  • queued, running, succeeded, failed, cancelled, or timed-out status
  • per-node status
  • logs
  • output previews
  • artifact references for large payloads
  • runner ownership and timing information

Inspect Output

Use run history when you need to understand what happened during execution. Select a run, inspect node status, and load full output when a preview is truncated.

Large outputs may be stored as artifacts instead of being shown inline. A truncated preview does not mean the node returned incomplete data. It only means the UI is showing a bounded preview.

Debug Runs

When a workflow does not behave as expected:

  1. Check whether the run reached a terminal status.
  2. Find the first failed or unexpected node.
  3. Inspect the node input, configuration, and output.
  4. Check whether templates resolved to the expected values.
  5. Retry with smaller input if the failure is hard to read.

Specialist Output

Specialist nodes can return generated text and metadata. If you need structured data downstream, configure the node for structured output or parse the text in a later node.

Security and Access

Workflow run and artifact access follows workspace membership and authorization rules. A user should only see runs and artifacts they are allowed to access in the workspace.

Next Steps