{"version":"2.1.273","anchor":"policy-limits-fetch-cycle-gains-accelerated-retry-and-netwo","canonical_anchor":"policy-limits-fetch-cycle-gains-accelerated-retry-and-netwo","heading":"Policy-limits fetch cycle gains accelerated retry and 'network kick' recovery","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/policy-limits-fetch-cycle-gains-accelerated-retry-and-netwo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Policy-limits fetch cycle gains accelerated retry and 'network kick' recovery\n\nClaude Code now retries faster and recovers sooner when it can't fetch your policy limits\n\n**Unclear.** Whether this behavior is active for this site's account is not established; the related gates are unread.\n\n**What**\n\nWhen Claude Code can't fetch your account's policy limits (usage\/permission rules from your organization) and has no recent valid result to fall back on, it now recovers more aggressively:\n\n- It arms a faster, randomized-timing retry instead of waiting for the normal poll interval\n\n- It also watches for any other successful network call and immediately re-tries the policy-limits fetch when one happens (a \"network kick\")\n\n- It now tracks how long it went without a valid result, and records that when a result is finally recovered\n\n**Why**\n\nThis should shorten the window where Claude Code is operating without confirmed policy limits, particularly after a temporary network hiccup, by recovering as soon as the network shows signs of life again rather than waiting out a fixed timer.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}