{"version":"2.1.295","anchor":"telemetry-exporter-drops-and-reports-unsent-events-at-shutdo","canonical_anchor":"telemetry-exporter-drops-and-reports-unsent-events-at-shutdo","heading":"Unsent usage data is counted as dropped when Claude Code shuts down","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/telemetry-exporter-drops-and-reports-unsent-events-at-shutdo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Unsent usage data is counted as dropped when Claude Code shuts down\n\nUnder an organisation's telemetry rules, usage data still waiting to be sent at shutdown is now recorded as dropped\n\n**What**\n\nClaude Code sends usage data, also called telemetry. When it shuts down while following an organisation's rules for that data, any events still waiting to be sent are now cleared and recorded as dropped because they were unsent at exit. Previously shutdown only tried to send everything still waiting.\n\n**Why**\n\nThis is internal bookkeeping about usage data and does not change how you use Claude Code.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}