Jobs and runs

A job is a single execution: either a script running once, or a flow running end to end. Triggering a flow — manually, on a schedule, from a webhook, or from any other trigger type — creates one top-level job for the flow plus one child job per step, each tracked and logged independently. “Run” is simply how the UI and this documentation refer to a job when you’re looking at its execution history — the Runs menu lists jobs, not a separate kind of object.

Job lifecycle

A queued job is either still waiting for a worker or actively executing; once it finishes, it’s recorded as one of:

Status	Description
`queued`	Accepted and waiting for a free worker.
`running`	Currently executing on a worker.
`success`	Finished without error.
`failure`	Exited with a non-zero status or threw an exception.
`canceled`	Stopped manually before completion, or superseded (e.g. by job debouncing).
`skipped`	A flow step whose branch condition wasn’t met.

A flow step configured with an approval step pauses that step until an approver responds (or a timeout elapses) rather than exposing a distinct top-level job status — the parent flow job stays running while the step waits.

Flow step data

Flow steps pass data to each other primarily through their inputs and outputs — a step’s result becomes available to the steps after it. For state that needs to be shared more loosely across a run without wiring it through every step’s inputs, Orvanta also provides flow user state and the shared directory.

Inspecting jobs

Via the UI

Open any script or flow in the dashboard and click the Runs tab, or use the workspace-wide Runs menu. Selecting a flow job shows its step-by-step status, each step’s own logs, and its result.

Via the CLI

# List recent jobs
orvanta job list

# Get a job's details (for flows, the step tree)
orvanta job get <id>

# Fetch a job's logs
orvanta job logs <id>

Retention

Job logs and results are retained according to your instance’s configured retention policy. Self-hosted deployments can configure retention in the platform settings.

Flows: How flows are structured and triggered.
Approval steps: Pause a flow step for human sign-off.
Monitor past and future runs: Filtering, labels, and batch actions in the Runs menu.
CLI: job: Full CLI reference for jobs.