opschain triggers show
triggers
opschain triggers show <project>/<code>
Shows a trigger's full definition as plain key: value lines — code, id,
name, description, enabled, subject, events, scope_path, the conditions
listed one per line (conditions: (none) when empty), action_type, the
action_params pretty-printed, throttle_per_minute, run_as, owned_by,
created_by and the timestamps — followed by the trigger's ten newest firings in the same
table triggers firings renders (no firings yet when it has none).
-o json|yaml prints both halves as one machine document:
{"trigger": …, "firings": …} (the firings capped at ten, as rendered).
Needs a server target (--server <url>, OPSCHAIN_SERVER, or the active
context).
Exit codes
| Code | Meaning |
|---|---|
| 0 | Trigger shown. |
| 1 | The command failed (trigger not found, server error). |
| 2 | Usage error — malformed address, no server target. |
Named errors
expected <project>/<trigger-code>, got "<arg>"— the positional argument carries no slash (exit 2).trigger "<code>" not found in project "<project>"— exit 1.
See also
opschain docs cli/triggers-firings— the full firing history with filters.opschain docs cli/triggers-export— the definition as re-importable YAML.