{"version":"2.1.247","anchor":"metrics-opt-out-check-no-longer-triggers-a-second-sign-in-re","canonical_anchor":"metrics-opt-out-check-no-longer-triggers-a-second-sign-in-re","heading":"Metrics opt-out check no longer triggers a second sign-in refresh","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/metrics-opt-out-check-no-longer-triggers-a-second-sign-in-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Metrics opt-out check no longer triggers a second sign-in refresh\n\nThe metrics opt-out check can no longer trigger a surprise second sign-in.\n\n**What**\n\nThe request that checks whether metrics logging is opted out is now tied to the session's existing credential and shares a one-shot refresh marker, so it cannot kick off its own re-authentication. Failures are classified as 401, 403, timeout, network error, 5xx, other 4xx or unknown. The telemetry shutdown wait is clamped by `CLAUDE_CODE_OTEL_SHUTDOWN_TIMEOUT_MS`.\n\n**Evidence**\n\n`gateToSessionOAuthCredential`\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_OTEL_SHUTDOWN_TIMEOUT_MS`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5"}