{"version":"2.1.280","anchor":"message-queue-tracks-an-urgent-lane-separately-in-backlog","canonical_anchor":"message-queue-tracks-an-urgent-lane-separately-in-backlog","heading":"Message queue tracks an 'urgent' lane separately in backlog reporting, and backoff can carry a resume timestamp","tier":"internal","area":"Message Queue","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/message-queue-tracks-an-urgent-lane-separately-in-backlog","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Message queue tracks an 'urgent' lane separately in backlog reporting, and backoff can carry a resume timestamp\n\nMessage queue backlog counts now include an 'urgent' lane, and backoff can store a fixed resume time\n\n**What**\n\nClaude Code's internal message queue now counts messages in a separate \"urgent\" lane toward its total unsent-message count, alongside messages already in flight or pending. The queue's backoff mechanism (which pauses retries after a failure) can now also be given an absolute timestamp marking when to resume, rather than only a duration to wait.\n\n**Why**\n\nThis makes backlog reporting account for urgent messages that weren't previously counted, and lets backoff pauses be scheduled to a specific resume time instead of only a relative delay.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}