You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ModelsArea: what it touches
ImprovementsKind: in v2.1.221,
What probably matters to youSection of the release
What
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.
Details
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.
Evidence
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.
