Dev.to1 min read
The 429 That Poisoned Every Fallback
Your agent has a fallback chain: GPT-5.4 → DeepSeek → Gemini Flash. GPT-5.4 hits a 429 rate limit. No problem — that's what fallbacks are for, right? Except DeepSeek never makes a request. It fails with the exact same error message and exact same error hash as the GPT-5.4 rejection. Then it gets put into cooldown. The Bug Issue #62672 documents this. Three providers configured: openai-codex/gpt-5.4 — OAuth, ChatGPT Plus deepseek/deepseek-chat — separate API key google/gemini-2.5-flash — separate
Read original on dev.to0
0Get the 10 best reads every Sunday
Curated by AI, voted by readers. Free forever.
Related
Hacker News
$500 GPU outperforms Claude Sonnet on coding benchmarks
Discussed on Hacker News with 377 points and 217 comments.
377
217Hacker News
Whistler: Live eBPF Programming from the Common Lisp REPL
Discussed on Hacker News with 115 points and 13 comments.
115
13Hacker News
Anthropic Subprocessor Changes
Discussed on Hacker News with 98 points and 44 comments.
98
44Liked this? Start your own feed.
0
0
Comment
Sign in to join the discussion.
Loading comments…