{"version":"2.1.312","anchor":"move-to-cloud-401-handler-now-gets-a-flag-and-may-retry","canonical_anchor":"move-to-cloud-401-handler-now-gets-a-flag-and-may-retry","heading":"Moving a session to the cloud retries a rejected sign-in in more cases","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/move-to-cloud-401-handler-now-gets-a-flag-and-may-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Moving a session to the cloud retries a rejected sign-in in more cases\n\nWhen moving a session to the cloud fails with a sign-in error, Claude Code can now retry even if the sign-in token did not change\n\n**What**\n\nWhen Claude Code moves a session to the cloud and the server rejects the request because of sign-in (an HTTP 401 error), Claude Code tries to refresh your sign-in. Before, it retried only if the refresh produced a different token. Now it also retries when a check on the original request says it should, even if the token is the same.\n\n**Why**\n\nIn practice, moving a session to the cloud should fail less often in the case where a retry was needed but the token had not changed.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}