{"version":"2.1.234","anchor":"signing-back-into-the-same-account-keeps-a-pending-auto-resu","canonical_anchor":"signing-back-into-the-same-account-keeps-a-pending-auto-resu","heading":"Signing back into the same account keeps a pending auto-resume","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/signing-back-into-the-same-account-keeps-a-pending-auto-resu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Signing back into the same account keeps a pending auto-resume\n\nSigning back into the same account keeps your pending wait-for-limit-reset resume instead of dropping it.\n\n**What**\n\nLogging in again with the same account no longer discards a pending \"wait for the usage limit to reset and continue\" claim. The logout path that clears cached state now takes an option to preserve it, and the OAuth re-login path sets that option by comparing the incoming account and organization identifiers with the current ones.\n\n**Details**\n\n- Applies wherever the usage-limit auto-resume feature is itself active.\n- A login as a different account still clears the state.\n\n**Evidence**\n\n`preserveQuotaAutoResume`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}