{"version":"2.1.274","anchor":"new-shutdown-time-telemetry-for-unsentbacklogged-events","canonical_anchor":"new-shutdown-time-telemetry-for-unsentbacklogged-events","heading":"New shutdown-time telemetry for unsent\/backlogged events","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-shutdown-time-telemetry-for-unsentbacklogged-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New shutdown-time telemetry for unsent\/backlogged events\n\nClaude Code now reports backlogged, unsent telemetry events when a session ends\n\n**What**\n\nClaude Code now tracks how many usage\/telemetry events are still waiting to be sent when a session shuts down. A new internal check reports the number of unsent client events, the number of unsent internal events, how long the oldest queued event has been waiting, and whether sending is currently backing off. This information is attached to telemetry as `unsent_client_events_at_close`, `unsent_internal_events_at_close`, and `hold_preflush_inflight_age_ms` at the moments a connection closes or no listener is holding events.\n\n**Why**\n\nThis gives visibility into whether Claude Code is losing or delaying telemetry data at shutdown, which helps diagnose gaps in usage reporting rather than leaving them silent.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}