{"version":"2.1.280","anchor":"self-hosted-runner-release-now-waits-for-post-turn-settling","canonical_anchor":"self-hosted-runner-release-now-waits-for-post-turn-settling","heading":"Self-hosted runner: release now waits for post-turn settling before releasing a session","tier":"use","area":"Self-Hosted Runner","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/self-hosted-runner-release-now-waits-for-post-turn-settling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Self-hosted runner: release now waits for post-turn settling before releasing a session\n\nSelf-hosted runner sessions now wait for post-turn settling before being released\n\n**What**\n\nOn a self-hosted runner, a session whose turn just finished is no longer released right away if it is still in a \"post-turn settling\" state. Release is now held until the finished turn has been reported to the server, bounded by a timeout set by `SELF_HOSTED_RUNNER_POST_TURN_SETTLE_MS`.\n\n**Why**\n\nThis avoids releasing a session before the server has confirmed the turn actually completed, reducing the chance of the session being reused or reported inconsistently.\n\n- Area: Self-Hosted Runner\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}