Self-hosted runners hold shutdown until a finished background task is read; the grace window is configurable.
What's wrong with this entry?
On self-hosted runners, a background task that has finished still counts as in-flight until the next turn reads its result, so drain and shutdown wait for it. The window is capped by SELF_HOSTED_RUNNER_BG_RESULT_GRACE_MS in milliseconds; setting it to 0 or an unusable value falls back to the default, so the hold cannot be turned off.
- The drain-wait help text documents the new hold and the fallback behaviour.
- The session runner records that a follow-up turn is pending and logs when the wait runs past the normal retire grace period.
SELF_HOSTED_RUNNER_BG_RESULT_GRACE_MS=5000 claudeSELF_HOSTED_RUNNER_BG_RESULT_GRACE_MS
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner