{"version":"2.1.271","anchor":"self-hosted-runner-poll-failure-paths-now-flag-a-fatal-exit","canonical_anchor":"self-hosted-runner-poll-failure-paths-now-flag-a-fatal-exit","heading":"Self-hosted runner poll-failure paths now flag a fatal-exit flag before breaking","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/self-hosted-runner-poll-failure-paths-now-flag-a-fatal-exit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Self-hosted runner poll-failure paths now flag a fatal-exit flag before breaking\n\nSelf-hosted runner now flags fatal-exit conditions before stopping on auth or repeated 404 poll failures\n\n**What**\n\nWhen the self-hosted runner's polling loop hits an authentication failure, or repeated 404 (not found) errors indicating its runner record no longer exists on the server, it now sets a flag marking the exit as fatal before breaking out of the loop.\n\n**Why**\n\nThis makes it clearer, internally, when the runner stopped because of an unrecoverable problem rather than a normal shutdown, which should help distinguish these failure cases in logs or exit handling.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}