opschain admin server site resume
Included from Basic tier
Lifts a site's quiesce posture — the explicit, audited operator act the site's held nodes wait for. Every node carrying the site identity rejoins within seconds: readiness returns, they contend for scheduler shards and leadership again, offer jobs and adopt runs; the site's runners fail back to their home servers on their next natural re-handshake. There is deliberately no automatic counterpart: no timer, sweep or boot path resumes a held site.
The verb can be sent to ANY node of the estate (the posture is one durable row every replica reads) — including a held node of the site 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 | Site resumed. |
| 1 | Request failed, the site was not quiesced, or the token was rejected. |
| 2 | Usage error — no site, or no server/credential resolvable. |
Named errors
this site holds no active quiesce posture— resume of an unheld site (exit 1,failed_precondition).
Examples
opschain admin server site resume dc2
See also
opschain docs cli/admin-server-site-quiesce— what the hold does.opschain docs cli/admin-server-site-list— what is held right now.