You'll notice
Useful4 Signal2
Signing back into the same account keeps your pending wait-for-limit-reset resume instead of dropping it.
What's wrong with this entry?
Anonymous. No account, no email.
What
Logging 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.
Details
- Applies wherever the usage-limit auto-resume feature is itself active.
- A login as a different account still clears the state.
Evidence
preserveQuotaAutoResume
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Login refresh tells "account on hold" apart from an expired token
Both mention auth
-
v2.1.235
Full "account on hold" sign-in path built but switched off
Both mention auth
-
v2.1.235
On-hold accounts get their own auth failure kind, behind the same gate
Both mention auth