opschain triggers discard
triggers
opschain triggers discard <project>/<code> --firing <firing-id>
Prunes one parked firing from a maintenance window's queue before the window
ends. Only a deferred firing can be discarded — find them with
opschain triggers firings <project>/<code> filtered to deferred. The
discarded firing settles suppressed with the discarding user named in its
error, and the window's release skips it: it never fires.
Discarding needs the same update right on the window node's maintenance rule path as starting and ending the window — it is a maintenance operation, not a trigger edit.
On success:
discarded firing <firing-id> of trigger <project>/<code> — settled suppressed, it will not release (-o json|yaml prints the settled firing
document instead). Needs a server target (--server <url>,
OPSCHAIN_SERVER, or the active context).
Flags
| Flag | Meaning |
|---|---|
--firing <id> | The deferred firing id to discard (required). |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Firing discarded. |
| 1 | The command failed (trigger or firing not found, the firing is not deferred, insufficient rights). |
| 2 | Usage error — missing --firing, malformed address, no server target. |
Named errors
expected <project>/<trigger-code>, got "<arg>"— exit 2.trigger "<code>" not found in project "<project>"— exit 1.- A non-deferred or unknown firing is refused by the server
(
POST .../firings/{id}/discard) and the API's error is printed — exit 1.
See also
opschain docs cli/triggers-firings— where deferred firings and their deferral reasons are listed.opschain learn 5.6(maintenance windows) — the deferral lifecycle this verb prunes.