{"version":"2.1.238","anchor":"self-hosted-runner-shutdown-defers-new-sessions-instead-of-r","canonical_anchor":"self-hosted-runner-shutdown-defers-new-sessions-instead-of-r","heading":"Self-hosted runner shutdown defers new sessions instead of refusing them outright","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/self-hosted-runner-shutdown-defers-new-sessions-instead-of-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Self-hosted runner shutdown defers new sessions instead of refusing them outright\n\nA shutting-down self-hosted runner now finishes assigned sessions instead of refusing them outright.\n\n**What**\n\nAfter a SIGTERM, the runner no longer immediately turns away work. A session assigned during shutdown is still served until a defer ceiling or its idle timer releases it, and a session that declines release because a user event is pending gets re-spawned. Only past the ceiling does the runner refuse to start it and put it back on the queue.\n\n**Details**\n\n- Applies to every self-hosted runner on this build; there is no flag.\n- The warning printed on a second signal now reads \"Another SIGTERM\" rather than \"A second SIGTERM\".\n\n**Evidence**\n\n`[runner:shutdown] defer ceiling reached (`\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}