Rate limit reach after resetting, then I'm out of Codex after running a 22minute job
Open
Nobody has claimed this yet.
app
bug
rate-limits
windows-os
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.818.61809
What subscription do you have?
Plus
What platform is your computer?
Windows
What issue are you seeing?
My usage rate was reset at 3:21pm. When I ran another job that took 22 minutes, it didn't complete and says I'm out of Codex again.
What steps can reproduce the bug?
Feedback ID: 019ff6d8-9823-7aa3-8a07-348cf98c3eb4
What is the expected behavior?
I'm hoping this is just a bug that needs to get worked out, but I'm a paid customer and have never ran into this issue before.
Additional information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Feedback ID 019ff6d8-9823-7aa3-8a07-348cf98c3eb4 and the reset at 3:21pm followed by a 22-minute job on Windows. Done means identifying why the paid Plus account was marked out of Codex after the reset and confirming that the job completes without prematurely exhausting usage.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100