{"version":"2.1.290","anchor":"tengu-sharded-beacon-gate-oauth-lock-timeout","canonical_anchor":"tengu-sharded-beacon-gate-oauth-lock-timeout","heading":"Specific error for subscribers when a sign-in refresh times out on an expired token","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/tengu-sharded-beacon-gate-oauth-lock-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Specific error for subscribers when a sign-in refresh times out on an expired token\n\nSubscribers whose sign-in token has expired get a dedicated error when Claude Code times out waiting to refresh it\n\n**Unclear.** It is not clear whether this behaves any differently from the previous build.\n\n**What**\n\nClaude Code signs subscription accounts in with a token, a saved credential that expires and has to be refreshed. While it refreshes, Claude Code holds a lock, a marker that stops two refreshes running at once. If you use a subscription, the wait for that lock times out, and your token has already expired, Claude Code stops with a dedicated error for that situation.\n\nThis check sits behind a server-controlled switch named `tengu_sharded_beacon`. When the server sends nothing, the switch counts as on.\n\n**Why**\n\nThe check looks the same as in the previous build, apart from internal renaming, so there may be no difference in what you see. If you do hit this error, it means the refresh could not finish in time and your saved sign-in had already expired.\n\n- Flag `tengu_sharded_beacon`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.290; this account: on, anonymous baseline: on, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}