getting `exceeded retry limit, last status: 429 Too Many Requests` over and over again, no recent changes to any configs
Open 💬 2 comments Opened May 18, 2026 by HenryDotApp
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.130.0
What subscription do you have?
Pro ($100/month)
Which model were you using?
gpt-5.5
What platform is your computer?
Darwin 24.5.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
iTerm2
Codex doctor report
What issue are you seeing?
Getting exceeded retry limit, last status: 429 Too Many Requests over and over again on work that was working fine for the duration of the time I've been using Codex up to today. Trying to continue the work just makes it run into the 429 again. Tried having Codex use no subagents and no tool calls and it ran into the 429 still.
Seems to be plenty of usage left as well, so it doesn't seem to be that
What steps can reproduce the bug?
Uploaded thread: 019d8d0f-c4bd-79f3-9536-8871526593d9
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
When 429 becomes the repeated terminal story, the useful thing is not more retries, it is a typed halt class with a cooldown receipt. Right now users get trapped in a fake-progress loop where Codex keeps proving that the same condition still exists. I would want the runtime to surface at least: provider scope, reset hint if known, retryable vs non-retryable class, and a do_not_retry_before timestamp. We ended up needing that same split in MartinLoop around API-budget and provider-limit loops.