{"version":"2.1.323","anchor":"metrics-opt-out-check-gets-a-hard-5s-timeout-wrapper","canonical_anchor":"metrics-opt-out-check-gets-a-hard-5s-timeout-wrapper","heading":"Metrics opt-out check is now strictly cut off after 5 seconds","tier":"notice","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/metrics-opt-out-check-gets-a-hard-5s-timeout-wrapper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Metrics opt-out check is now strictly cut off after 5 seconds\n\nThe check for whether metrics are enabled now stops for certain after 5 seconds instead of relying on a plain timeout option\n\n**What**\n\nClaude Code checks with the server whether metrics (usage measurements) are enabled. That check already had a 5-second limit set as an option. It now uses a timer that actively cancels the request when 5 seconds pass.\n\n**Why**\n\nA slow or stuck answer can no longer hold up Claude Code's startup.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}