You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Usage limit reset failed and my quota is gone #31601
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
I had 3 usage limits and I tried to reset using Codex CLI, it failed. I thought something went wrong so I clicked reset again in the Codex App and it failed again. Now I just wasted 2 of my resets and nothing I could do. Any help or reimbursement of the resets?
What steps can reproduce the bug?
/usage and claim reset
What is the expected behavior?
No response
Additional information
thread ID 019eb4e4-df86-7652-982a-0847ba18d131 No response
+1 Seems you, me and many others are also stuck with this - and my reset seems not to be for another 6 days so I cannot work
I hope Open AI will fix this soon. https://github.com/openai/codex/issues/31450
Additional datapoint from an account that burned 3 banked resets in under an hour (2026-07-18, ~11:30–12:35 UTC), while status incident 01KXT44TAQQ2R0AZDDVSJGAC4H was open:
GET /backend-api/wham/usage with a valid Codex CLI OAuth token (claims: chatgpt_plan_type=pro, issued 2026-07-17 ~21:20 UTC) and the correct chatgpt-account-id header returned plan_type: "free", a 30-day window, and rate_limit_reset_credits: { available_count: 0, total_earned_count: 0 } — while the UI still showed 3 banked resets as redeemable. All 3 were consumed with zero effect (rate_limit_reset_ineligible path).
UPDATE / correction for accuracy: on this account the free plan_type turned out to be legitimate — the paid plan's billing period had ended the previous day (renewal canceled earlier in the month). So this wasn't backend entitlement misresolution here. But the defect this issue tracks still fired in full:
the UI presented 3 banked resets as available and redeemable on an ineligible account,
each redemption was accepted and decremented the bank,
none applied, and nothing warned redemption would be void,
the OAuth token still claimed pro a day after period end — mixed signals everywhere.
Redemption must be transactional (don't consume unless the reset lands) and ineligible accounts shouldn't be offered the redeem action at all. Reported to support with full ids (cases 11695130/11695466/11695477).
Adding a data point on the "reset consumed but quota not restored" problem: there is no way for a user to verify it either way.
I redeemed all three of my weekly reset credits. None of them appears in /usage daily, and none appears in the CLI's local telemetry: rate_limits carries no field tying a reading to a specific window or credit (limit_id is the literal string codex for essentially every reading, limit_name is always null). So a reset that restores nothing is indistinguishable from one that works.
Reconstructed series from my own account, with the reset anchors, in #36307 (comment).
Activity
github-actions commentedon Jul 8, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
otpl8855-hash commentedon Jul 8, 2026
I had the same issue 20 mins back, 1 reset is wasted
weihao-ma commentedon Jul 9, 2026
same here
fbernklau commentedon Jul 9, 2026
Same on my end. It consumed the reset but did not reset the quota.
omniassist commentedon Jul 9, 2026
+1 Seems you, me and many others are also stuck with this - and my reset seems not to be for another 6 days so I cannot work
I hope Open AI will fix this soon. https://github.com/openai/codex/issues/31450
Other examples:
#31575
#31606
KibaekJeong commentedon Jul 10, 2026
i got the same issue here
Elendizzie commentedon Jul 10, 2026
Can someone relay the message to OAI? This is insane and nobody even cares?
gflengas commentedon Jul 10, 2026
just got this as well from the cli... i had 2 more resets that expire soonish so i used one more from the codex app in macOS and it worked...
zongjing1998 commentedon Jul 16, 2026
ChatGPT Plus, Codex Desktop on Windows.
The Usage UI shows 3 available Full resets, but using the first reset fails.
Backend log:
POST /wham/rate-limit-reset-credits/consume
HTTP 403
{"detail":{"code":"rate_limit_reset_ineligible"}}
Signing out and signing back in did not resolve it.
The reset count remains at 3 and weekly usage remains at 0%.
boujunck commentedon Jul 16, 2026
same
What version of Codex CLI are you using?
v0.144.4
What subscription do you have?
Plus
What platform is your computer?
macOs
daniel-mf-92 commentedon Jul 18, 2026
Additional datapoint from an account that burned 3 banked resets in under an hour (2026-07-18, ~11:30–12:35 UTC), while status incident 01KXT44TAQQ2R0AZDDVSJGAC4H was open:
GET /backend-api/wham/usagewith a valid Codex CLI OAuth token (claims:chatgpt_plan_type=pro, issued 2026-07-17 ~21:20 UTC) and the correctchatgpt-account-idheader returnedplan_type: "free", a 30-day window, andrate_limit_reset_credits: { available_count: 0, total_earned_count: 0 }— while the UI still showed 3 banked resets as redeemable. All 3 were consumed with zero effect (rate_limit_reset_ineligiblepath).UPDATE / correction for accuracy: on this account the free plan_type turned out to be legitimate — the paid plan's billing period had ended the previous day (renewal canceled earlier in the month). So this wasn't backend entitlement misresolution here. But the defect this issue tracks still fired in full:
proa day after period end — mixed signals everywhere.Redemption must be transactional (don't consume unless the reset lands) and ineligible accounts shouldn't be offered the redeem action at all. Reported to support with full ids (cases 11695130/11695466/11695477).
phyrexia commentedon Jul 31, 2026
Adding a data point on the "reset consumed but quota not restored" problem: there is no way for a user to verify it either way.
I redeemed all three of my weekly reset credits. None of them appears in
/usage daily, and none appears in the CLI's local telemetry:rate_limitscarries no field tying a reading to a specific window or credit (limit_idis the literal stringcodexfor essentially every reading,limit_nameis always null). So a reset that restores nothing is indistinguishable from one that works.Reconstructed series from my own account, with the reset anchors, in #36307 (comment).
jinlonghh commentedon Sep 4, 2026
周限额用完了,使用额度重置一直显示无法加载用量限制重置信息