{"version":"2.1.318","anchor":"program-use-case-404-handling","canonical_anchor":"program-use-case-404-handling","heading":"A background request stops labelling its purpose after that label is rejected","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/program-use-case-404-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A background request stops labelling its purpose after that label is rejected\n\nIf a side request that labels the turn's use case gets a not-found error, Claude Code stops sending that label for that model for the turn\n\n**What**\n\nClaude Code sometimes makes small side requests alongside the main one, and these can carry a label for what the current turn is being used for. If such a request comes back with a 404, meaning the server did not recognise it, Claude Code now stops sending that label for that model for the rest of the turn. Before, only two other kinds of rejection were handled this way.\n\n**Why**\n\nOne rejected label no longer keeps tripping up later requests in the same turn.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}