{"version":"2.1.285","anchor":"3p-telemetry-events-queue-until-a-collector-road-is-install","canonical_anchor":"3p-telemetry-events-queue-until-a-collector-road-is-install","heading":"Early telemetry records wait for a destination instead of being lost","tier":"notice","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/3p-telemetry-events-queue-until-a-collector-road-is-install","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Early telemetry records wait for a destination instead of being lost\n\nTelemetry records created before a collector is ready are now held and sent later, up to a limit\n\n**What**\n\nTelemetry records sent to an outside collector, a service that receives usage data, are now held until the route to that collector is set up. Before, they were dispatched straight away even when no route was open.\n\nThe number held is capped. Past that cap, new records are dropped and Claude Code logs the warning `[3P telemetry] Event record dropped: no road installed and too many already waiting for one`.\n\n**Why**\n\nRecords from the first moments of a session are no longer lost just because the collector was not ready yet. If you see the warning, some records were still dropped.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}