opschain admin runner-group resume
Included from Basic tier
opschain admin runner-group resume <name>
Lifts a group's drain (the v2 RunnerService.SetRunnerGroupDraining RPC) so the
group's runners are offered work again. This clears only the group-level
flag: a runner that was also drained individually stays quiesced until
opschain admin runner resume clears its own flag — admin runners list
distinguishes the scopes in its STATE column.
A drained runner's poll is held for the poll window (50 s by default) before it polls again, so the resume reaches each member on its next poll — at most one poll window after the command.
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
The server's acknowledgement, as JSON (-o yaml for YAML):
{
"draining": false,
"name": "secure"
}
An info:runner:group_drain_changed event records the change.
Exit codes
0 resumed; 1 the request failed (unknown group, network, rejected token); 2 usage.
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(exit 1)- An unknown group name reports the server's 404 (exit 1).
See also
opschain docs cli/admin-runner-group-drain— the verb this undoes.opschain docs cli/admin-runner-resume— lift a single runner's drain.opschain docs fleet-queue— the dispatch plane the group rejoins.