opschain admin runner resume
Included from Basic tier
opschain admin runner resume <runner-id>
Lifts a runner's drain (the v2 RunnerService.SetRunnerDraining RPC) so it is offered
work again. This clears only the runner's own drain flag: a runner whose
group is draining stays quiesced until the group is resumed too
(opschain admin runner-group resume) — admin runners list shows the
remaining scope as (group) in the STATE column.
A drained runner's poll is held for the poll window (50 s by default) before the runner polls again, so the resume reaches it on that 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,
"id": "<runner-id>"
}
An info:runner:drain_changed event records the change.
Exit codes
0 resumed; 1 the request failed (unknown runner id, 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)
See also
opschain docs cli/admin-runner-drain— the verb this undoes.opschain docs cli/admin-runner-group-resume— lift a group-wide drain.opschain docs fleet-queue— the dispatch plane the runner rejoins.