{"version":"2.1.309","anchor":"sandbox-ask-and-oauth-side-query-fixes","canonical_anchor":"sandbox-ask-and-oauth-side-query-fixes","heading":"Some sign-in errors on side requests no longer trigger a token refresh","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandbox-ask-and-oauth-side-query-fixes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Some sign-in errors on side requests no longer trigger a token refresh\n\nSome background requests now skip the login token refresh on certain sign-in errors, and the log message for a failed refresh reports the right details\n\n**Unclear.** Which sign-in errors now skip the token refresh is not stated.\n\n**What**\n\nBesides the main conversation, Claude Code sometimes sends smaller side requests to the model. When one of these fails with a sign-in error, Claude Code normally tries to refresh your login token (the credential that proves you are signed in) and retry. For a particular kind of failure it now skips the refresh and reports the error straight away.\n\nThe log message written when a refresh attempt fails now reports the correct status and details. Before, it read from the wrong values.\n\n**Why**\n\nSome sign-in errors on these side requests no longer cause a pointless refresh attempt. If you read Claude Code's logs while tracking down a sign-in problem, the refresh failure message now describes what actually happened.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}