{"version":"2.1.290","anchor":"beta-header-400-retry-check-now-also-matches-non-400-errors","canonical_anchor":"beta-header-400-retry-check-now-also-matches-non-400-errors","heading":"Fallback for unsupported API beta options can now follow other error types","tier":"notice","area":"API Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/beta-header-400-retry-check-now-also-matches-non-400-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Fallback for unsupported API beta options can now follow other error types\n\nClaude Code can now match API errors other than status 400 to the beta options it sent, so its fallback may trigger more often\n\n**Unclear.** It is not clear what kinds of error the new check matches.\n\n**What**\n\nBeta headers are optional labels Claude Code sends to the API to turn on features that are still in testing. When a request fails, Claude Code tries to work out whether one of those labels caused it. Before, it only did this for errors with status 400. It now runs an extra check on errors of any status. The older check, which reads the error message, still applies only to status 400.\n\n**Why**\n\nThe fallback for unsupported beta headers may now kick in for errors it previously ignored.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}