{"version":"2.1.281","anchor":"rejection-classifier-drops-ok-response-early-return","canonical_anchor":"rejection-classifier-drops-ok-response-early-return","heading":"Rejection classifier drops ok-response early return","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/rejection-classifier-drops-ok-response-early-return","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Rejection classifier drops ok-response early return\n\nHandling of 400, 403 and 415 errors now reads the response text directly when checking for invalid_json_at_origin\n\n**Unclear.** The finding does not say whether any error messages or retries change as a result.\n\n**What**\n\nClaude Code has a step that sorts rejected requests with the statuses 400, 403 and 415 into categories. That step no longer starts by checking whether the response was successful. When it looks for the `invalid_json_at_origin` case, it now reads the response text directly.\n\n**Why**\n\nThis is internal error handling, and the finding does not describe anything you would see differently."}