{"version":"2.1.265","anchor":"oauth-refresh-lock-telemetry-no-longer-crashes-the-release-p","canonical_anchor":"oauth-refresh-lock-telemetry-no-longer-crashes-the-release-p","heading":"OAuth refresh-lock telemetry no longer crashes the release path","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/oauth-refresh-lock-telemetry-no-longer-crashes-the-release-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### OAuth refresh-lock telemetry no longer crashes the release path\n\nA telemetry failure can no longer block releasing the OAuth token refresh lock\n\n**What**\n\nWhen Claude Code releases its internal lock on refreshing an OAuth authentication token, it emits telemetry events for 'releasing' and, on error, 'release_error'. Both of these telemetry calls are now individually wrapped in their own error handling, so a failure in sending the telemetry itself can no longer prevent the lock from actually being released or the error from being logged.\n\n**Why**\n\nThis is a reliability fix: previously, a telemetry hiccup during token refresh could interfere with releasing the lock or recording the error, which could affect authentication flows. Now the telemetry is best-effort and can't get in the way.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}