{"version":"2.1.285","anchor":"content-filter-error-classification-now-requires-a-400-statu","canonical_anchor":"content-filter-error-classification-now-requires-a-400-statu","heading":"Content filter errors are now identified more precisely","tier":"notice","area":"API Errors","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/content-filter-error-classification-now-requires-a-400-statu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Content filter errors are now identified more precisely\n\nAn error now counts as blocked by the content filter only if the API returned status 400 or no status, not whenever the text appears\n\n**What**\n\nWhen the API refuses to return output because of its content filtering policy, the error says \"Output blocked by content filtering policy\". Claude Code used to label any error containing that text as a content filter block. It now does so only when the error's status code, the number the API returns to describe a failure, is 400 or missing.\n\n**Why**\n\nOther errors that happen to mention that text are no longer reported as content filter blocks, so the reason Claude Code gives for a failure is more accurate.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}