opschain admin platform attempt
Included from Basic tier
Disposes one suspended step attempt during a runner-plane halt — the v2
PlatformService.SetAttemptDisposition call naming the run, the step and
the disposition.
A halt under the default suspend mode freezes in-flight attempts in place
(SIGSTOP / container pause) so they can be inspected; once forensics on an
attempt are done, this verb decides its fate individually:
--disposition resume— continue the attempt in place while the halt still holds for everything else.--disposition kill— cancel the attempt.
opschain admin platform attempt <run-id> <step-id> --disposition <resume|kill>
Flags
| Flag | Meaning |
|---|---|
--disposition <d> | resume (continue in place while the halt holds) or kill (cancel the attempt) (required). |
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
Output is the server's response document — JSON, or YAML under -o yaml.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Disposition applied. |
| 1 | Request failed, the server refused (e.g. no such suspended attempt), or the token was rejected. |
| 2 | Usage error — wrong argument count, missing disposition, or no server/credential resolvable. |
Named errors
a server is required — pass --server <url>, set OPSCHAIN_SERVER, or 'opschain context use <name>'— exit 2.this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login'— exit 2.the server rejected the credential — run 'opschain login' again, or check the admin token— HTTP 401 (exit 1).
Examples
opschain admin platform attempt 01999a7e 0199a1c2 --disposition kill
See also
opschain docs cli/admin-platform-halt— where attempts get suspended, and the complete-instead-of-suspend alternative.opschain docs cli/admin-queue— the leases those attempts hold.