opschain maintenance end
maintenance
opschain maintenance end <path>
Ends the node's active maintenance window. The gate lifts, the
triggerable api:nodes:maintenance_ended event is emitted on the node
path, and the firings the window deferred are released in original
event order, each re-evaluated against the world as it now is
(conditions, throttle, authorisation and the rest all run again); a
deferral parked past a manual window's declared end intent expires as
suppressed instead of firing. Ending is the only way a manual window
closes — the intent declared at start is advisory.
A scheduled window that has not started yet is not ended but cancelled —
opschain maintenance cancel.
Prints ended maintenance on <path> (window <id>); -o json / -o yaml
emit the ended window document. The path takes the same bare form as the
other maintenance verbs (acme/environments/dev).
Exit codes
| Code | Meaning |
|---|---|
| 0 | Window ended. |
| 1 | The server refused — e.g. no active window on the node, or missing rights. |
| 2 | Usage error, including a missing server target. |
Named errors
expected a node path like demo/environments/dev, got ""— exit 2.
Example
opschain maintenance end acme/environments/dev
ended maintenance on /projects/acme/environments/dev (window 01999a7e-…)
See also
opschain docs cli/maintenance-status— the deferred count before you release it.opschain learn 5.6— exactly how release re-evaluates each firing.