{"version":"2.1.238","anchor":"retry-classifier-labels-errors-that-carry-a-type-but-no-stat","canonical_anchor":"retry-classifier-labels-errors-that-carry-a-type-but-no-stat","heading":"Retry classifier labels errors that carry a type but no status","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/retry-classifier-labels-errors-that-carry-a-type-but-no-stat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Retry classifier labels errors that carry a type but no status\n\nErrors hidden inside a successful response now get their own retry label instead of being unclassified.\n\n**What**\n\nErrors returned inside an otherwise successful response, which have an error type but no HTTP status, now get their own label built from an `in_band_` prefix plus the error type. This branch runs before the existing server error and modified-thinking-blocks cases.\n\n**Evidence**\n\n`thinking_blocks_modified`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}