{"version":"2.1.310","anchor":"more-api-errors-are-classified-as-unsupported-role-errors","canonical_anchor":"more-api-errors-are-classified-as-unsupported-role-errors","heading":"More provider errors are recognised as message role errors","tier":"notice","area":"API Providers","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/more-api-errors-are-classified-as-unsupported-role-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### More provider errors are recognised as message role errors\n\nClaude Code now treats more API errors as errors about an unsupported message role, not just those mentioning \"Unexpected role\"\n\n**What**\n\nEach message sent to a model has a role, such as user or assistant. Some providers reject a role they do not support. Claude Code used to recognise this kind of error only when it said \"Unexpected role\" along with \"input message role\". It now also recognises a further pattern of error text, so more errors from providers are treated as this kind.\n\n**Why**\n\nMore of these errors now get the handling Claude Code already gives to role errors, rather than being treated as some other failure.\n\n- Area: API Providers\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}