opschain activities list
Included from Basic tier
Lists the newest activities — changes and workflow runs, merged — from the
targeted server (GET /api/activities). Each row is one denormalised
activity: when it last moved, whether it is a change, a workflow_run or
(with --background-tasks) a node_background_task, its status, what ran
(the change's action, the run's workflow code, or the background task's
type) and the node it ran against.
The table is UPDATED TYPE STATUS WHAT TARGET ID; TARGET is the
innermost parent node's self link. -o json / -o yaml emit the activity
resources verbatim.
Flags
| Flag | Meaning |
|---|---|
--limit <n> | Newest activities to return (default 100; the server caps a page at 1000). |
--background-tasks | Also show node background tasks (actions refreshes) in the feed (filter[background_tasks]=1). Default off: without the flag the feed is exactly the change/workflow-run union. Task rows show the task type in WHAT and the owning node in TARGET, and join the --filter vocabulary like any other row. |
--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 newest 1000 activities (the server cap) are fetched and filtered, then --limit truncates the result. Grammar: opschain docs cli. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Listed (an empty feed prints no activities and still exits 0). |
| 1 | The lookup failed — server, auth or decode error. |
| 2 | Usage error, including a missing server target. |
Named errors
activities need a server target — pass --server <url> or 'opschain context use <name>' (local mode has no activities)— run without a server target (exit 2).
Examples
opschain activities list
opschain activities list --limit 500 -o json
opschain activities list --background-tasks --filter type=node_background_task
See also
opschain docs cli/scheduled-activities-list— what is going to run.opschain docs cli/events— per-event detail with correlation ids.