opschain triggers disable
triggers
opschain triggers disable <project>/<code>
Disables a trigger: a one-attribute update (enabled: false) over the
ordinary authorised update endpoint
(PATCH /api/projects/{project}/triggers/{id}). A disabled trigger matches
nothing and records no firings; its definition and firing history are
untouched, so triggers enable restores it exactly. Prefer this over
deleting when the automation should merely pause.
On success: disabled trigger <project>/<code> (-o json|yaml prints the
server's response document instead). Needs a server target
(--server <url>, OPSCHAIN_SERVER, or the active context).
Exit codes
| Code | Meaning |
|---|---|
| 0 | Trigger disabled. |
| 1 | The command failed (trigger not found, server refused the update). |
| 2 | Usage error — malformed address, no server target. |
Named errors
expected <project>/<trigger-code>, got "<arg>"— exit 2.trigger "<code>" not found in project "<project>"— exit 1.
See also
opschain docs cli/triggers-enable.opschain docs cli/triggers-delete— removal rather than a pause.