Rate-limit rejections now feed a controller that can arm or cancel an automatic resume after a quota block.
What's wrong with this entry?
The rate-limit tracker now emits an event when a rejected request is observed, and a controller subscribes to it to re-arm or cancel an automatic resume after a quota block. None of the identifiers for this subsystem exist in the previous build.
- The tracker gained a rejection event and a subscribe helper; the controller reacts by re-arming a cap or emitting a cancellation event.
- What turns the controller on is decided elsewhere; nothing in the tracker itself gates it.
tengu_quota_auto_resume_cancelled
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.239
Spend and rate limit notices say when the limit resets
Both mention rate limit
-
v2.1.239
Spend limits are now recognised as rate limits
Both mention rate limit
-
v2.1.239
The "wrap up" hint no longer fires for the 5-hour window
Both mention rate limit