{"version":"2.1.301","anchor":"self-hosted-runner-release-retries-and-failure-reporting","canonical_anchor":"self-hosted-runner-release-retries-and-failure-reporting","heading":"Self-hosted runners handle failed session releases more consistently","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/self-hosted-runner-release-retries-and-failure-reporting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Self-hosted runners handle failed session releases more consistently\n\nOn self-hosted runners, failed session releases now log how many failed in a row and always restart the idle timer\n\n**What**\n\nA self-hosted runner is a machine you run yourself to host Claude Code sessions. When the runner tries to release a session that has gone idle and the release fails or is declined, it now:\n\n- logs how many releases have failed in a row\n\n- restarts the idle timer, so it tries again later\n\nBefore, each kind of failure was logged on its own and some did not restart the timer. Reasons for a session failing are now cleaned before they are reported, except when the reason is that the source reference could not be found.\n\n**Why**\n\nRetrying the release of idle sessions on self-hosted runners now behaves the same way whatever caused the failure.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}