{"version":"2.1.317","anchor":"side-queries-retry-without-a-rejected-program-use-case-id","canonical_anchor":"side-queries-retry-without-a-rejected-program-use-case-id","heading":"Background requests retry when the server rejects a use-case label","tier":"internal","area":"API","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/side-queries-retry-without-a-rejected-program-use-case-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Background requests retry when the server rejects a use-case label\n\nBackground requests now retry without their use-case label if the server rejects it, and stop sending that label for the rest of the run\n\n**What**\n\nSome requests Claude Code sends to the model in the background, apart from your main conversation, can carry a label naming a program use case. When the server rejects that label or refuses the use case, Claude Code now sends the request again without the label. It then stops sending the label for as long as that Claude Code process keeps running.\n\nThis only matters when a request carries such a label in the first place.\n\n**Why**\n\nA rejected label no longer causes these background requests to fail. They go through without it.\n\n- Area: API\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}