Skip to main content
Version: v5.8.0

opschain runs refuse

Included from Basic tier

opschain runs refuse <run-id> <step> --reason <text> [--evidence name=file]... [--reference name=system:id]...

Refuses a manual step the run is holding: you will not (or cannot) perform the activity, and say why. The step fails with manual step refused by <principal id>: <reason> and its on_error: applies — with none, the run fails. The refusal is recorded on the run's chain (audit:runs:refused) with your principal id. <step> is the step's id, full path or name. Evidence is optional and takes the same kinds as opschain runs attest (opschain docs cli/runs-attest); a refusal fills no outputs.

Who may refuse is decided exactly as who may attest. In the local lane (--local) run it from another terminal; the attached run picks it up.

Flags​

FlagMeaning
--reason <text>Why the step is refused (required, at most 4000 bytes).
--evidence name=fileAn evidence file (repeatable).
--reference name=system:idAn identifier the external system minted (repeatable).

Output​

refused manual step release/verify-domain of run 0199c81e-… — the step fails: another tenant owns the domain

-o json|yaml prints the stored refusal in the StepAttestation shape (opschain docs resources/step_attestation), outcome refused and the reason as note: id, run_id, step_id, step_path, outcome, principal_id, answered_at, title, activity, command, where, evidence_class, evidence (the BreakglassEvidence keys), note, outputs, correlation_id; empty fields omitted.

Exit codes​

CodeMeaning
0Refused.
1The refusal was refused — the step is not awaiting attestation, or you hold no attest grant.
2Usage error (missing --reason).

Named errors​

  • required flag(s) "reason" not set — exit 2.
  • run <id> has no manual step "<step>" (its manual steps: …) — exit 1.
  • The manual step is not awaiting attestation: it is in the "<state>" state — exit 1.