refusals-and-fallback changedbuild-with-claude/refusals-and-fallback
Nearest release: v2.1.316, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+6added
Lines−6removed
From line
12
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits31to this page, all time
The whole hunk
from line 12, old and new numbered
/
from line 12
1212 - claude-sonnet-5-5
1313 - claude-haiku-5-5
1414 supportedPlatforms:
15 Claude API: ga
16 Claude Platform on AWS: ga
17 Claude Models on Google Cloud (Anthropic managed): ga
18 Amazon Bedrock: ga
19 Claude Models on Google Cloud (Google managed): ga
20 Microsoft Foundry: ga
15 Claude API: stable
16 Claude Platform on AWS: stable
17 Claude Models on Google Cloud (Anthropic managed): stable
18 Amazon Bedrock: stable
19 Claude Models on Google Cloud (Google managed): stable
20 Microsoft Foundry: stable
2121---
2222
2323Claude Fable 5.1, Claude Fable 5, Claude Opus 5.5, Claude Opus 5, Claude Sonnet 5.5, and Claude Haiku 5.5 include safety classifiers that can decline a request. When that happens, you receive a normal response, not an error, with `stop_reason: "refusal"`. Its `stop_details.category` names the policy area (see [What a refusal looks like](https://platform.claude.com/docs/en/build-with-claude/refusals-and-fallback#refusal-response)). You can usually still get an answer by sending the same request to another Claude model. This page shows you how to recognize a refusal and how to set up that retry.
No line in this hunk matches that.