{"version":"2.1.309","anchor":"session-runner-skip-duplicate-release-for-silent-startup-ch","canonical_anchor":"session-runner-skip-duplicate-release-for-silent-startup-ch","heading":"Remote session runner no longer releases a silent session twice","tier":"internal","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/session-runner-skip-duplicate-release-for-silent-startup-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote session runner no longer releases a silent session twice\n\nIf a session being started printed nothing and is already being released, the runner now leaves that release alone instead of starting another\n\n**What**\n\nThe runner that starts remote sessions sometimes releases a session it has handed out. If a session it was starting printed nothing and a release is already under way, the runner now leaves it to that release instead of starting a second one. The self-hosted runner also reports this case separately.\n\n**Why**\n\nThis prevents two releases of the same session clashing in remote 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"}