Some accounts now see an estimated reset time on the rate-limit banner; others see none.
What's wrong with this entry?
When you are rate limited and no known reset time is available, the banner computes a projected time, but only for accounts whose low-priority-offer experiment arm is set to "treatment". Everyone in the control arm sees the previous behaviour, with no time shown.
- The projected value is used only when neither an active rate-limit phase nor a known reset timestamp supplies one.
- The arm value arrives from server-side configuration, so nothing in this build decides who is in it.
lowPriorityOffer
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.234
Rate-limit prompts resolve model aliases to the model that actually answers
Both mention rate limit
-
v2.1.234
Quota rejections feed a new auto-resume controller
Both mention rate limit
-
v2.1.239
Spend and rate limit notices say when the limit resets
Both mention rate limit