Codex usage reset succeeded but quota remains at 0%, and two reset credits were consumed
What version of the Codex App are you using (From “About Codex” dialog)?
26.707.41301
What subscription do you have?
plus
What platform is your computer?
Darwin 24.6.0 x86_64 i386
What issue are you seeing?
Hello OpenAI Support,
I am experiencing an issue with my Codex usage limit and usage reset credits.
I had reached my Codex usage limit, so I redeemed a usage reset credit. Codex displayed a message confirming that the reset was successful. However, after the reset:
- My Codex usage still showed 0% remaining.
- I was still unable to start or continue Codex tasks.
- Refreshing and reopening Codex did not resolve the issue.
I initially assumed that this was a temporary display or synchronization bug. I therefore redeemed a second usage reset credit, but the same thing happened again: the reset was reported as successful, while the available usage remained at 0% and Codex was still unavailable.
As a result, two usage reset credits appear to have been consumed without restoring any usable Codex quota.
Environment:
- Product: Codex desktop app
- Operating system: macOS
- Account plan: ChatGPT Plus
- Issue type: Usage limit / reset credit / quota synchronization
- Current displayed remaining usage: 0%
Expected behavior:
After redeeming a usage reset credit, my Codex usage allowance should be restored and I should be able to continue using Codex.
Actual behavior:
Codex confirms that the reset succeeded, but the available quota remains at 0%, Codex remains unusable, and the reset credit is consumed.
Could you please:
- Investigate whether the usage resets were correctly applied to my account.
- Restore the two reset credits that were consumed without restoring usage.
- Correct or resynchronize my Codex usage allowance.
- Confirm whether this is related to a known quota-accounting or reset-credit issue.
I can provide screenshots showing the successful reset confirmation, the 0% usage display, and any relevant timestamps if needed.
Thank you.
<img width="1356" height="860" alt="Image" src="https://github.com/user-attachments/assets/8f05b8cf-be5e-4299-90f3-f7c1f664ca0c" />
<img width="331" height="242" alt="Image" src="https://github.com/user-attachments/assets/cad2211f-3699-48ca-9eb0-eb7fedf537e8" />
What steps can reproduce the bug?
Feedback ID: no-active-thread-019f4efb-cd87-77e2-887d-a1aa6217e551
What is the expected behavior?
_No response_
Additional information
_No response_
8 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Yes, I had exactly the same issue that occured to you occur to me accept I only lost one of the 2 resets I had available. Frustrating. Hopefully they can fix this bug
I also had this exact same issue.
Yes same issue here.
Same issue here. The reset opportunity has been used up, but the quota has not been reset.
I encountered what appears to be the same issue.
I contacted OpenAI Support. They told me that, according to their backend records, the redemption succeeded and they found
Follow-up with the key detail from my support case:
OpenAI Support stated that they found no evidence that the redemption failed or was only partially applied. However, they were unable to explain why, immediately after I redeemed a Full reset (Weekly + 5 hr) at approximately 2026-07-12 07:00 UTC, both meters briefly showed 100% remaining, and then the weekly meter reverted to 0% after I reopened the Usage page, while the reset balance remained reduced from 3 to 2.
Support's position is that subsequent usage
Additional affected account reporting the same failure.
Please inspect the server-side redemption transaction, restore the consumed reset credit or the intended weekly allowance, and prevent remaining credits from being consumed by the same failure. The paid subscription was canceled immediately afterward because the paid coding service remained unavailable after the credit was consumed.
No personal account identifiers are included here; they can be provided securely to OpenAI Support.