{"version":"2.1.267","anchor":"worker-event-uploads-now-carry-holdbatch-metadata-upload","canonical_anchor":"new-ccr-telemetry-gate-upload-hold-marker","heading":"CCR event uploads gain hold\/drain telemetry","tier":"soon","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/worker-event-uploads-now-carry-holdbatch-metadata-upload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### CCR event uploads gain hold\/drain telemetry\n\nClaude Code Remote (cloud runner) event uploads now report hold and drain metadata behind a new gate\n\n**What**\n\n- A new `uploadHoldMarker` setting (gate `tengu_ccr_upload_hold_marker`, off by default) controls whether the upload-hold telemetry below is included at all.\n\n- When enabled, worker event uploads sent to `\/worker\/events` and `\/worker\/internal-events` attach an `upload_hold` object with details such as `held`, `flush_reason`, `held_count`, `hold_age_ms`, `inflight_retry_count`, `hold_rule`, and `post_index`.\n\n- The upload queue now tracks per-lane counters (posts, rows, max rows per post, failed posts, dropped rows, and more), and fires a new `ccr_upload_drain` telemetry event with lane, trigger, held events\/time, posts, rows, failed posts, dropped rows, and drain duration whenever a batch finishes draining.\n\n**Why**\n\nThis gives better visibility into how CCR (Claude Code Remote, the cloud runner) batches and delays event uploads, which helps diagnose upload backlogs or data loss, without changing behavior while the gate stays off.\n\n- Area: Telemetry\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5"}