opschain admin server resume
Included from Basic tier
Resumes dispatch after a quiesce — the v2 RunnerService.ResumeFleet RPC. Offers to
runners restart and the work that parked during the hold dispatches normally;
nothing else changes, since a quiesce never touched leases or in-flight
steps.
Flags
| Flag | Meaning |
|---|---|
--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 | Dispatch resumed. |
| 1 | Request failed or the token was rejected. |
| 2 | Usage error — 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 server resume
See also
opschain docs cli/admin-server-quiesce— the hold this lifts.opschain docs cli/admin-platform-resume— resuming a halted plane is a different, posture-row-named verb.