Runs

A run is a single execution instance of a workflow. Every time a workflow is triggered — manually, on a schedule, or via webhook — Orvanta creates a new run with its own isolated context, logs, and audit trail.

Run lifecycle

Queued → Running → Succeeded
                 → Failed
                 → Cancelled
                 → Awaiting approval  (when a ConsentGate is active)

Status	Description
queued	The run has been accepted and is waiting for a worker.
running	At least one node is currently executing.
awaiting_approval	A ConsentGate node is waiting for human sign-off.
succeeded	All nodes completed without error.
failed	At least one node exited with a non-zero status or threw an exception.
cancelled	The run was manually cancelled before completion.

Run context

Each run carries a context — a key-value store that flows through the workflow. Nodes can read from and write to the context, allowing data to pass between steps without external state.

Context values are typed (string, number, boolean, JSON object) and are stored in the run record for full auditability.

Inspecting runs

Via the UI

Open any workflow in the dashboard and click the Runs tab. Select a run to see its node-by-node execution timeline, logs, and context snapshot.

Via the CLI

# List recent runs for a workflow
orvanta runs list --workflow my-workflow

# Stream logs for a specific run
orvanta runs logs <run-id>

# Show the context snapshot at the end of a run
orvanta runs context <run-id>

Retention

Run logs and context snapshots are retained for 90 days on Orvanta Cloud by default. Self-hosted deployments can configure retention in the platform settings.

Related

• Workflows — How workflows are structured and triggered.
• ConsentGate — Human approval step that puts a run in awaiting_approval.
• CLI: /runs — Full CLI reference for runs.