exceeded retry limit, last status: 401 Unauthorized, request id: 997429a61bc2252c-SIN
Resolved 💬 6 comments Opened Oct 31, 2025 by fwends Closed Nov 15, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
latest
What subscription do you have?
pro
Which model were you using?
_No response_
What platform is your computer?
_No response_
What issue are you seeing?
TMI
What steps can reproduce the bug?
Uploaded thread: 019a301b-2e49-7c73-b7f9-bfa36da0ffa4
What is the expected behavior?
_No response_
Additional information
All I'm trying to do is continue with the chat and it just keeps retrying until it times out.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for reporting the issue. You mentioned you're using the "latest" version. Can you be more specific? Are you using the CLI or the IDE extension?
Have you tried logging out and logging back in? Did that resolve the problem?
I'm using the CLI and I would just like to bring up the reason that I only put "latest."
You've got so much form filling and fields that you want. I'm so used to bug reporting in Claude where it's just instant and it carries all that information over. Maybe you could take something from them and make it a bit easier for us users to report a bug that helps your product.
It's way to much friction on codex to want to use it as much
Thanks for the suggestion. We recently added a
/feedbackslash command that you can use within the CLI.Well, that's interesting because that's exactly what I used. That submitted the two log files or whatever it submits.
Then it took me to GitHub and asked me to fill out all those fields.
The problem you encountered appears to be related to token refresh. We've think we've fixed the underlying bug more recent versions of the CLI. I'm going to close this issue, but if you see a similar issue with the latest version of the CLI, please open a new bug report.