Fast mode stays on and shows an error notification when credit limits reject overage.
What's wrong with this entry?
When the server rejects fast-mode overage for a credit-limit reason, the fastMode user setting is left alone and you get an error notification explaining why.
- Applies to reasons out_of_credits, org_spend_cap_reached and org_level_disabled_until.
- Posts an immediate error notification keyed "fast-mode-overage-rejected" carrying the human-readable reason.
- Repeats within the same turn are suppressed.
- Rejections for any other reason still disable fast mode as before.
Fast mode credits rejection already surfaced this turn, suppressing repeat
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.219
Fast mode unavailability reworked into machine-readable reason codes
Both mention fast mode model
-
v2.1.248
Auto mode can be switched off server-side when /fast is on
Both mention fast mode
-
v2.1.219
SDK reports why fast mode is unavailable
Both mention fast mode