{"version":"2.1.314","anchor":"self-hosted-runner-idle-release-goes-through-a-retrying-wra","canonical_anchor":"self-hosted-runner-idle-release-goes-through-a-retrying-wra","heading":"Self-hosted runners release idle sessions through a status-reporting helper","tier":"internal","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/self-hosted-runner-idle-release-goes-through-a-retrying-wra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Self-hosted runners release idle sessions through a status-reporting helper\n\nA self-hosted runner now releases an idle session through a helper that reports status and can be stopped, instead of in a single direct call\n\n**Unclear.** It is not certain that the warm-up report was really removed.\n\n**What**\n\nA self-hosted runner is a machine you run yourself to pick up work. When it lets go of a session it is no longer using, it now does so through a helper that reports its status and can be told to stop, instead of making a single direct call. The runner's report that its first network warm-up had finished has also been removed from its polling loop.\n\n**Why**\n\nThis changes how self-hosted runners poll for work and release sessions.\n\n- Area: Self-Hosted Runners\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}