opschain maintenance extend
maintenance
opschain maintenance extend <path> --by <duration> | --to <rfc3339>
Moves the active window's end later: the hard end of a scheduled
window, the advisory until of a manual one. Exactly one of the two
flags is required, and they are mutually exclusive. Extending never
shortens a window — to finish earlier, use opschain maintenance end.
Prints extended maintenance on <path> until <new-end> (window <id>);
-o json / -o yaml emit the updated window document.
Flags
| Flag | Meaning |
|---|---|
--by <duration> | How much to add to the window's current end (e.g. 1h, 30m). Sent as whole seconds. |
--to <rfc3339> | The window's new end, as an absolute RFC3339 timestamp. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Window extended. |
| 1 | The server refused — e.g. no active window on the node, or the new end is not later. |
| 2 | Usage error. |
Named errors
pass --by (e.g. 1h) or --to (an RFC3339 timestamp)— neither flag; exit 2.pass --by or --to, not both— exit 2.--by wants a positive duration like 15m or 1h— exit 2.--to wants an RFC3339 timestamp like 2026-10-12T22:00:00Z: <parse error>— exit 2.expected a node path like demo/environments/dev, got ""— exit 2.
Examples
opschain maintenance extend acme/environments/prod --by 30m
opschain maintenance extend acme/environments/prod --to 2026-10-17T15:00:00Z
See also
opschain docs cli/maintenance-schedule— automatic extension while the window's own work runs.opschain docs cli/maintenance-end.