claude-code - 💡(How to fix) Fix [DOCS] Policy refusal errors missing Request ID guidance in error reference [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56496Fetched 2026-05-06 06:26:30
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Error Message

"Find your error" and "Report an error" on the Error reference page

This page lists runtime errors Claude Code displays and how to recover from each one, plus what to check when responses seem off without an error. | API Error: 500 ... Internal server error | Server errors | | API Error: Repeated 529 Overloaded errors | Server errors | | API Error: 400 due to tool use concurrency issues | Request errors | If an error is not listed here or the suggested fix does not help: The Error reference page does not document policy refusal errors as a distinct runtime error case, and it does not explain that refusal messages now include the API Request ID for support debugging in v2.1.129.

A. Missing refusal-error coverage

Users who hit a policy refusal cannot find that message in the runtime error index, even though the page claims to cover Claude Code runtime errors. Add a new refusal/policy error section to the Error reference page and include the new Request ID support workflow.

Policy refusal error

[example refusal error message including the API Request ID]

  • Review the refusal explanation shown in the error message | https://code.claude.com/docs/en/errors | 9-11, 17-50 | Error index claims to cover runtime errors but does not list refusal/policy errors | | https://code.claude.com/docs/en/errors | 531-536 | Report-an-error guidance omits the new Request ID detail for support follow-up | | https://platform.claude.com/docs/en/api/errors | n/a | Cross-reference: platform docs already describe Request IDs in API error responses | Relevant changelog context: this behavior changed in v2.1.129, so the Claude Code error-reference page should mention that refusal messages now surface the API Request ID for debugging and support.

Code Example

> [example refusal error message including the API Request ID]
>
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/errors

Section/Topic

"Find your error" and "Report an error" on the Error reference page

Current Documentation

The page currently frames itself as the place to look up Claude Code runtime errors, but it does not document policy refusal errors or mention Request IDs:

This page lists runtime errors Claude Code displays and how to recover from each one, plus what to check when responses seem off without an error.

MessageSection
API Error: 500 ... Internal server errorServer errors
API Error: Repeated 529 Overloaded errorsServer errors
Request timed outServer errors, or Network if the message mentions your internet connection
...
API Error: 400 due to tool use concurrency issuesRequest errors
Responses seem lower quality than usualResponse quality

Later, the support guidance says:

If an error is not listed here or the suggested fix does not help:

  • Run /feedback inside Claude Code to send the transcript and a description to Anthropic.
  • Run /doctor to check for local configuration problems
  • Check status.claude.com for active incidents
  • Search existing issues on GitHub

What's Wrong or Missing?

The Error reference page does not document policy refusal errors as a distinct runtime error case, and it does not explain that refusal messages now include the API Request ID for support debugging in v2.1.129.

That leaves two gaps:

A. Missing refusal-error coverage

Users who hit a policy refusal cannot find that message in the runtime error index, even though the page claims to cover Claude Code runtime errors.

B. Missing Request ID support guidance

The page tells users to use /feedback or contact support, but it does not tell them to include the API Request ID now shown in refusal errors, which is the key detail that makes those reports easier to investigate.

Suggested Improvement

Add a new refusal/policy error section to the Error reference page and include the new Request ID support workflow.

Suggested content:

Policy refusal error

Claude rejected the request for policy reasons.

[example refusal error message including the API Request ID]

What to do:

  • Review the refusal explanation shown in the error message
  • If you contact Anthropic support or file /feedback, include the API Request ID from the refusal message
  • Retry only after changing the request if the refusal explains a prompt/content policy problem

If the exact message text varies by surface, the page could document the pattern instead of one rigid string, but it should still call out that the API Request ID is now included and should be preserved in support reports.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/errors9-11, 17-50Error index claims to cover runtime errors but does not list refusal/policy errors
https://code.claude.com/docs/en/errors531-536Report-an-error guidance omits the new Request ID detail for support follow-up
https://platform.claude.com/docs/en/api/errorsn/aCross-reference: platform docs already describe Request IDs in API error responses

Total scope: 2 Claude Code sections affected, with one relevant platform cross-reference

Relevant changelog context: this behavior changed in v2.1.129, so the Claude Code error-reference page should mention that refusal messages now surface the API Request ID for debugging and support.

extent analysis

TL;DR

Add a new section to the Error reference page to document policy refusal errors and include guidance on using the API Request ID for support.

Guidance

  • Identify the exact location where the new policy refusal error section should be added, likely in the "Find your error" section of the Error reference page.
  • Determine the correct format for documenting the API Request ID in refusal error messages, considering the possibility of varying message text across different surfaces.
  • Update the "Report an error" guidance to instruct users to include the API Request ID when contacting support or filing a /feedback report.
  • Review the changelog and platform documentation to ensure consistency in describing the new behavior introduced in v2.1.129.

Example

### Policy refusal error
Claude rejected the request for policy reasons.
[example refusal error message including the API Request ID]
**What to do:**
* Review the refusal explanation shown in the error message
* If you contact Anthropic support or file `/feedback`, include the API Request ID from the refusal message
* Retry only after changing the request if the refusal explains a prompt/content policy problem

Notes

The suggested improvement should be implemented in a way that is consistent with the existing documentation style and formatting.

Recommendation

Apply workaround: Add the new policy refusal error section and update the support guidance to include the API Request ID, as this will improve the usability of the Error reference page and facilitate easier support debugging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING