{"version":"2.1.268","anchor":"event-queue-batching-gains-partial-passowed-bookkeeping","canonical_anchor":"event-queue-batching-gains-partial-passowed-bookkeeping","heading":"Event-queue batching gains partial-pass\/'owed' bookkeeping","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/event-queue-batching-gains-partial-passowed-bookkeeping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Event-queue batching gains partial-pass\/'owed' bookkeeping\n\nThe batched event-send queue now tracks 'owed' events and can let some events through while holding others back\n\n**What**\n\nThe generic queue Claude Code uses to batch and send events was reworked. `takeBatch` now takes an explicit count of how many events are sendable, tracks an `owed` counter for events that were pulled ahead of a hold, and supports a `holdSpec.passes` setting that lets certain events through even while a hold is otherwise in effect. The `send` and `onDrained` callbacks now also receive a `rule` field explaining why events were held back.\n\n**Why**\n\nThis is internal bookkeeping for how events get batched and released; it makes the hold-and-flush logic more precise about which events are let through and why, without changing what data ends up being sent.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}