{"version":"2.1.277","anchor":"ccr-client-event-uploads-now-record-queue-position-diagnosti","canonical_anchor":"ccr-client-event-uploads-now-record-queue-position-diagnosti","heading":"CCR client-event uploads now record queue-position diagnostics per frame","tier":"internal","area":"CCR","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/ccr-client-event-uploads-now-record-queue-position-diagnosti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### CCR client-event uploads now record queue-position diagnostics per frame\n\nClient telemetry uploads now record what each event was queued behind before sending\n\n**What**\n\nWhen Claude Code uploads tracked telemetry events, each upload is now tagged with a timestamp of when it was queued (`enqueuedAtMs`) and a classification of what it was waiting behind before being sent: a hold, a durable post, an ephemeral post, a retry backoff, or nothing.\n\n**Why**\n\nThis is a diagnostic addition that lets Claude Code's telemetry pipeline distinguish delays caused by queuing behind other uploads from delays caused by retries or other holds, which helps pinpoint where event-reporting slowdowns come from.\n\n- Area: CCR\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}