{"version":"2.1.282","anchor":"error-code-table-in-a-bundled-doc-now-covers-redacted-thinki","canonical_anchor":"error-code-table-in-a-bundled-doc-now-covers-redacted-thinki","heading":"Bundled error table now lists rejected redacted thinking data","tier":"internal","area":"Thinking","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/error-code-table-in-a-bundled-doc-now-covers-redacted-thinki","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Bundled error table now lists rejected redacted thinking data\n\nA documentation table bundled with Claude Code now groups rejected redacted_thinking data with thinking signature errors\n\n**What**\n\nClaude Code ships with a documentation table describing categories of errors the API can return. The `thinking_signature` category used to list only errors about thinking signatures. It now also covers the API rejecting the data in a redacted_thinking block, reported as \"Invalid data in redacted_thinking block\". Thinking is the model's reasoning before it answers, and a redacted_thinking block is reasoning returned in hidden form.\n\n**Why**\n\nIn practice, the documentation now treats this rejection as the same kind of problem as a bad thinking signature.\n\n- Area: Thinking\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}