openai / openai/codex

Two Codex limit resets used 52 minutes apart; first reset did not appear to work

Open
#44,300 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What issue are you seeing?

Hi OpenAI Support,

I’m reporting an issue where I had to use two Codex limit reset credits before I could continue working.

My reset history shows:

  • First reset: September 10, 2:25 AM GMT+7
  • Second reset: September 10, 3:17 AM GMT+7
  • Time between resets: 52 minutes

Before using the first reset, my remaining quota was approximately 5%. After using it, I submitted a new prompt, but Codex reported that
I had reached the usage limit and showed 0% remaining, without producing useful output.

I did not complete any meaningful work between the two resets. I eventually used the second reset, which allowed me to continue.

Could you please investigate:

  1. Whether the first reset successfully restored my eligible quota.
  2. If it did, which limit I reached again and what usage was recorded between the two resets.
  3. Whether resets can be used while some quota remains, or whether the quota must reach 0% first.

Please check the redemption records and quota changes around both timestamps. If the first reset credit was consumed without
successfully resetting my eligible quota, I would appreciate having that credit restored.

Thank you.

What steps can reproduce the bug?

Uploaded thread: 01a087d2-b805-7113-ade9-b3f8024e498d

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the uploaded thread 01a087d2-b805-7113-ade9-b3f8024e498d and the reset history around September 10, 2:25–3:17 AM GMT+7. Done would require confirming whether the first reset restored quota, identifying any intervening usage or limit, and resolving the requested credit restoration if it did not.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.