opschain chains
Included from Basic tier
Inspect correlation chains: the causal cascade of events, changes and
workflow runs that share one correlation id. Every chain member's API
attributes carry correlation_id, so any row of opschain events (or any
change/run id that started a cascade) is a handle into its whole chain.
chain is accepted as an alias.
Two verbs with different jobs:
| Subcommand | Does |
|---|---|
opschain chains show | The whole cascade as a causality tree: objects with derived lifecycle, informative events kept, lifecycle noise folded — opschain docs cli/chains-show |
opschain chains triage | Failures only, plus the server's triage digest: each suspect's failure class, topology, runner and log tail; a green chain digests to its caveats; --bundle exports the redacted support bundle — opschain docs cli/chains-triage |
show is for understanding what happened; triage is for deciding what to do about a failure. Reach for triage first when something is red — it already filters to the failed objects, attributes a shared runner, and hands you the retry and log commands.
Both verbs need a server target (--server <url> or the active context);
local mode has no chains.
See also
opschain docs cli/events— finding a correlation id when none is known yet.opschain learn 5.1— the guided events-and-chains triage flow.