{"version":"2.1.233","anchor":"truncated-event-batches-are-flagged-and-pending-events-are-d","canonical_anchor":"truncated-event-batches-are-flagged-and-pending-events-are-d","heading":"Truncated event batches are flagged, and pending events are drained on interrupt","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/truncated-event-batches-are-flagged-and-pending-events-are-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Truncated event batches are flagged, and pending events are drained on interrupt\n\nWhen background event batches get cut short, Claude is told how many events are still waiting.\n\n**What**\n\nWhen background events are delivered to Claude in batches, a batch cut short by size or count limits now says so in a system note, and each attachment carries a count of how many events are still waiting, so the model knows nothing was silently dropped.\n\n**Details**\n\n- Batches that hit the size or count limit append a \"delivery chunked\" note rather than ending mid-list with no signal.\n- Cancelling the queue settles every undelivered event as dropped with the reason \"interrupt cleared the queue\", instead of leaving them unresolved.\n- These event attachments are also now kept out of one transcript-collapsing path, so they stay visible in history.\n\n**Evidence**\n\n`delivery chunked: `\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}