After a second refusal fallback, you still return to the model you originally started on.
What's wrong with this entry?
If a model refusal already moved you to a fallback model, a second refusal now updates only the fallback target instead of replacing the whole record. The originally recorded model survives, so coming back off the fallback returns you to the model you actually started with.
replaceRefusalFallbackModelLatch
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.220
Opus 5 is skipped when the client cannot see model entitlements
Both mention model fallback
-
v2.1.220
Refusal fallback no longer picks Opus 5 when entitlements are unknown
Both mention model fallback
-
v2.1.222
Model refusal fallback updates the shown model
Both mention model fallback