{"version":"2.1.282","anchor":"concurrent-401-handlers-share-the-forced-outcome","canonical_anchor":"concurrent-401-handlers-share-the-forced-outcome","heading":"Requests that fail sign-in at the same moment now get the same result","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/concurrent-401-handlers-share-the-forced-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Requests that fail sign-in at the same moment now get the same result\n\nWhen several requests are refused as not signed in at once, every one of them now receives the same outcome from the single sign-in refresh\n\n**Unclear.** It is not settled whether this actually changes the login prompts a reader sees.\n\n**What**\n\nA 401 is the response a server sends when it does not accept your sign-in. When several of Claude Code's requests get a 401 at the same time, they share one refresh of your sign-in instead of each starting its own. The requests that join a refresh already in progress now also receive the final outcome that refresh decided on. Before, they only got the basic result of the refresh.\n\n**Why**\n\nEvery request caught in the same sign-in failure should now end up handled the same way. This may remove mismatched login prompts when several requests fail at once.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}