{"version":"2.1.268","anchor":"event-queue-batching-gains-configurable-hold-rules-with-byte","canonical_anchor":"event-queue-batching-gains-configurable-hold-rules-with-byte","heading":"Event queue batching gains configurable hold rules with byte\/item caps and named release reasons","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/event-queue-batching-gains-configurable-hold-rules-with-byte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Event queue batching gains configurable hold rules with byte\/item caps and named release reasons\n\nInternal event batching now supports configurable size\/age limits and reports why a batch was released\n\n**What**\n\nAn internal queue used for batching and throttling events has been reworked to support configurable hold rules: limits on the number of items, total byte size, and maximum age before a batch is released. Each release now also reports which named rule triggered it, alongside the existing release reasons like hitting a maximum item count, byte size, age, or capacity.\n\n**Why**\n\nThis is internal plumbing rather than a user-facing feature, but it gives Claude Code finer control over how event data is grouped and flushed, which can affect performance and telemetry accuracy.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}