opschain admin server node resume
Included from Basic tier
Lifts a server node's quiesce posture — the explicit, audited operator act a held node waits for. The named node (held after a quiesce, or booted held under a durable posture) rejoins within seconds: it re-enters readiness, contends for scheduler shards and leadership again, offers jobs and adopts runs. There is deliberately no automatic counterpart: no timer, sweep or boot path resumes a held node.
The verb can be sent to ANY node of the estate (the posture is one durable row every replica reads) — including the held node itself, whose API keeps answering while held.
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). |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Node resumed. |
| 1 | Request failed, the node was not quiesced, or the token was rejected. |
| 2 | Usage error — no name, or no server/credential resolvable. |
Named errors
this server node holds no active quiesce posture— resume of an unheld node (exit 1,failed_precondition).
Examples
opschain admin server node resume node-a
See also
opschain docs cli/admin-server-node-quiesce— what the hold does.opschain docs cli/admin-server-node-list— what is held right now.