{"version":"2.1.323","anchor":"rate-limit-retry-persistent-429-retry-can-be-limited-to-ove","canonical_anchor":"rate-limit-retry-persistent-429-retry-can-be-limited-to-ove","heading":"Endless retry on rate limits can now be limited to overload errors only","tier":"use","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rate-limit-retry-persistent-429-retry-can-be-limited-to-ove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Endless retry on rate limits can now be limited to overload errors only\n\nA new option can stop persistent sessions from retrying forever on rate-limit errors, so they fall back to the usual retry handling\n\n**Unclear.** How `persistentOverloadOnly` is turned on is not stated.\n\n**What**\n\nWhen Anthropic's servers return a rate-limit error (code 429, meaning too many requests), sessions using persistent retry used to retry forever. A new option, `persistentOverloadOnly`, changes this. When it is set to true, a rate-limit error no longer triggers endless retries. It goes to the usual handling instead, which may switch to a fallback model or retry a limited number of times.\n\n**Why**\n\nThis changes how long-running or unattended sessions behave when they hit rate limits.\n\n- Area: API Requests\n- Names: `persistentOverloadOnly`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}