{"version":"2.1.248","anchor":"token-refresh-lock-timeouts-get-their-own-error-label","canonical_anchor":"token-refresh-lock-timeouts-get-their-own-error-label","heading":"Token refresh lock timeouts get their own error label","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/token-refresh-lock-timeouts-get-their-own-error-label","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Token refresh lock timeouts get their own error label\n\nLogin token refresh lock timeouts get their own error label in logs.\n\n**What**\n\nWhen a login token refresh cannot get its lock in time, the failure is now classified as `oauth_refresh_lock_timeout` rather than falling into the generic bucket, and it is logged the same way as auth errors and revoked tokens. Unconditional.\n\n**Evidence**\n\n`oauth_refresh_lock_timeout`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}