{"version":"2.1.319","anchor":"self-hosted-runner-poll-backoff-no-longer-capped-by-server","canonical_anchor":"self-hosted-runner-poll-backoff-no-longer-capped-by-server","heading":"Self-hosted runners drop an extra limit on retry delays","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/self-hosted-runner-poll-backoff-no-longer-capped-by-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Self-hosted runners drop an extra limit on retry delays\n\nAfter a failed poll, self-hosted runners now work out their wait before retrying without an extra limit that applied before\n\n**Unclear.** What the removed limit was based on is not settled, so how much retry timing changes is unclear.\n\n**What**\n\nA self-hosted runner is a machine you run yourself that picks up Claude Code work by checking in, or polling, regularly. When a poll fails, the runner waits before trying again. That wait is now worked out without an extra limit that used to cap it.\n\n**Why**\n\nIf you operate self-hosted runners, the timing of retries after failed polls may differ from before.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: org\n- Heads-up: no"}