{"version":"2.1.269","anchor":"new-api-error-classification-helper-overloadedrate-limits","canonical_anchor":"new-api-error-classification-helper-overloadedrate-limits","heading":"New API-error classification helper (overloaded\/rate_limit\/server_error\/other)","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-api-error-classification-helper-overloadedrate-limits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New API-error classification helper (overloaded\/rate_limit\/server_error\/other)\n\nNew helper sorts unrecognized API error messages into overloaded, rate_limit, server_error, or other\n\n**What**\n\nA new pair of functions checks whether a message is an API error that doesn't already match a known, specific error case, and if so, sorts its `.error` field into one of four buckets: `overloaded`, `rate_limit`, `server_error`, or `other`.\n\n**Why**\n\nThis gives Claude Code a consistent way to categorize API errors it doesn't have specific handling for, which likely feeds into how errors are logged or reported.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}