opschain maintenance status

maintenance

opschain maintenance status <path>

Shows the node's maintenance window, if any: its state (scheduled, active or ended), reason, timing (from/to for a scheduled window with its auto-extension settings and opening runs; the declared until for a manual one), who started and ended it, the three allow lists, and the live count of deferred trigger firings parked behind it. When the count is non-zero, a hint names the opschain triggers commands that list and discard the parked firings.

With no window the command prints no active maintenance window on <path> — the node operates normally and still exits 0. With -o json / -o yaml the window document is emitted, or {"active": false} when there is none — a stable shape for scripting the gate.

The path takes the same bare form as the other maintenance verbs: acme/environments/dev means /projects/acme/environments/dev.

Exit codes

Code	Meaning
0	Status shown — window or not.
1	The lookup failed — server, auth or decode error.
2	Usage error, including a missing server target.

Named errors

• expected a node path like demo/environments/dev, got "" — exit 2.

Example

opschain maintenance status acme/environments/dev
node:        /projects/acme/environments/dev
window:      01999a7e-…
state:       active
active:      true
reason:      db engine upgrade
until:       2026-10-12T22:00:00Z
started_by:  alice
started_at:  2026-10-12T20:00:03Z
allow workflows: db_upgrade
allow actions:   (none)
allow users:     dba_bot
deferred firings: 0

See also

• opschain docs cli/maintenance-list — every window across the estate.
• opschain learn 5.6 — what a deferred firing is and how it releases.