{"version":"2.1.275","anchor":"command-queue-draining-now-accounts-for-stale-classifier-s","canonical_anchor":"command-queue-draining-now-accounts-for-stale-classifier-s","heading":"Command queue draining now accounts for 'stale' classifier screening on submitted prompts","tier":"notice","area":"Message Queue","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/command-queue-draining-now-accounts-for-stale-classifier-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Command queue draining now accounts for 'stale' classifier screening on submitted prompts\n\nQueued prompts now stop batching together once a stale screening result is detected\n\n**What**\n\nWhen Claude Code drains a queue of pending prompt messages to send them together, it now checks each one's \"screening\" status (a classifier check run when the prompt was submitted). If a queued message's screening is considered stale, the queue now stops accumulating further messages at that point, rather than always draining the entire run of same-mode messages as before.\n\n**Why**\n\nThis avoids batching a prompt whose classifier screening is out of date together with other queued prompts, which could otherwise let a stale screening result apply to messages it wasn't actually checked against.\n\n- Area: Message Queue\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}