Skip to main content

orun status

orun status shows the execution status of the latest run or a specific execution.

Usage

orun status

Common examples

Show the latest execution:

orun status

Show all executions:

orun status --all

Show step-level detail for the latest execution:

orun status --detailed

Show a specific execution:

orun status --exec-id my-plan-20240601-a1b2c3

Output

The default view shows a compact execution header followed by a job list sorted by priority (running first, then failed, then completed, then pending):

EXECUTION my-plan-20240601-a1b2c3  ● running  4/38 jobs  2m
Plan: my-plan

● api-edge-worker@production.deploy 12s
✓ platform-shared@production.build 8s
○ web-console@staging.deploy

The --all view lists all executions with running ones sorted first:

EXECUTION                              STATUS        PLAN                 JOBS      DURATION      AGE
● my-plan-20240601-a1b2c3 running my-plan 4/38 2m now
✓ my-plan-20240531-d4e5f6 completed my-plan 38/38 4m12s 1d

Status icons

IconMeaning
Running
Completed
Failed
Pending

Flags

FlagMeaning
--exec-idShow a specific execution by ID
--allList all stored executions
--detailedInclude step-level status in the output
--jsonOutput in JSON format
--watch, -wContinuously refresh until the run reaches a terminal state
--intervalRefresh interval for --watch (default 1s)
--remote-stateFetch status from orun-backend instead of local state
--backend-urlorun-backend URL for remote state (or set ORUN_BACKEND_URL)

Remote status

When --remote-state is set, orun status fetches run and job state from the backend rather than the local .orun/ store.

orun status \
--remote-state \
--backend-url https://orun-backend.example.com \
--exec-id gh-12345678-1-a1b2c3

The same rendering is used for local and remote state. --watch polls the backend until the run reaches a terminal state (completed or failed). --json returns machine-readable output.

Use orun describe run <id> for a fuller breakdown including metadata, timing, and job-level errors.