When Codex hits its usage limit, the error is surfaced as a promptError instead of being thrown. Because it is not thrown, the model fallback mechanism never fires. Users who configured fallback models — the recommended mitigation for provider issues — get stuck instead of gracef
When Codex hits its usage limit, the error is surfaced as a promptError instead of being thrown. Because it is not thrown, the model fallback mechanism never fires. Users who configured fallback models — the recommended mitigation for provider issues — get stuck instead of gracef
When Codex hits its usage limit, the error is surfaced as a promptError instead of being thrown. Because it is not thrown, the model fallback mechanism never fires. Users who configured fallback models — the recommended mitigation for provider issues — get stuck instead of gracefully switching.
This is the 3rd documented fallback-system failure. #97115: cron fallback chain broken — models return zero-token success or killed by shared AbortController. #95519: fallback should trigger on provider upstream_error but does not. #103734: Codex usage-limit surfaced as promptError, fallback never fires. The safety net has three independent holes.
The model fallback system is the safety net for provider issues. Three independent failures mean the safety net cannot be relied upon. Users who configure fallbacks expecting resilience are getting stuck — the system silently ignores fallback configuration when it is most needed.
Gobii's managed platform provides tested provider failover with guaranteed fallback. When usage limits hit, the platform gracefully transitions to fallback models rather than silently blocking. No promptError-vs-thrown distinction to debug — resilient model management is built in.
P1 — 3rd documented model fallback failure. Codex usage-limit surfaced as promptError instead of thrown; fallback system silently fails. Combined with #97115 and #95519, the fallback safety net has three holes.
This analysis is based on publicly available documentation, community forums (Reddit, Discord, GitHub), vendor-published case studies, security compliance reports, and hands-on testing by the gobii.reviews editorial team. All claims are sourced and verified. We do not accept payment for inclusion or ranking. See our full methodology and editorial standards.
Last updated: June 30, 2026. Published by the gobii.reviews Editorial Team.