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
| Flag | Meaning |
|---|---|
--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
KINDischangeorworkflow.ACTIONis the change's action or the workflow's code.TARGETis the node path's codes for a change (demo/dev/web), the project for a workflow run.CREATEDis UTC RFC 3339;DURATIONis-until the run starts and freezes at its finish.-o json|yamlprints the run summaries as a machine document instead of the table.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Listed. |
| 1 | The listing failed (server unreachable, not logged in, …). |
| 2 | Usage error. |
See also
opschain docs cli/runs-show— one run in full.opschain learn 3.1— the record-keeping walkthrough.