Skip to main content
Version: v5.7.0

opschain runs list

Included from Basic tier

opschain runs list [--limit <n>]

Lists runs, newest first — changes and workflow runs in one table. Locally it reads the repository's run store; against a server (--server, OPSCHAIN_SERVER or the active context) it reads the v2 ChangeService.ListChanges and WorkflowRunService.ListWorkflowRuns RPCs, merges the two families, sorts by creation time and truncates to the limit.

Flags​

FlagMeaning
--limit <n>Maximum runs to list (default 50). Against a server the limit is also passed to each family's listing, then applied again to the merged result.
--filter <column>[!]=<value>Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased (spaces/dashes fold to _); * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. With --filter, the listing is fetched without the server limit, filtered, then --limit truncates the result. Grammar: opschain docs cli.

Output​

ID KIND ACTION TARGET STATUS CREATED DURATION
  • KIND is change or workflow. ACTION is the change's action or the workflow's code. TARGET is the node path's codes for a change (demo/dev/web), the project for a workflow run.
  • CREATED is UTC RFC 3339; DURATION is - until the run starts and freezes at its finish.
  • -o json|yaml prints the run summaries as a machine document instead of the table.

Exit codes​

CodeMeaning
0Listed.
1The listing failed (server unreachable, not logged in, …).
2Usage error.

See also​

  • opschain docs cli/runs-show — one run in full.
  • opschain learn 3.1 — the record-keeping walkthrough.