Repository navigation
Codex rate-limit bug: banked reset consumed, 94% weekly quota dropped to 0% #44221
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.903.8094.0 Codex CLI：0.154.0-alpha.3
What subscription do you have?
ChatGPT Pro20X
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Hi, I’d like to report a suspected incorrectly applied banked Codex reset and request an account-level investigation.
I used my banked reset today, September 10, 2026 (China Standard Time, UTC+8). At the time, my weekly usage page was still showing approximately 94% allowance/usage status.
After I consumed the banked reset, my Usage page subsequently changed unexpectedly: my weekly usage window was recalculated/reset, and my scheduled weekly reset date changed from September 16 to September 12.
However, the banked reset I had just used was still marked as consumed and was not restored.
This appears to be a usage-window/reset-accounting inconsistency rather than a request for a courtesy reset. The banked reset was consumed immediately before the system recalculated my weekly allowance and reset schedule, so the benefit associated with that banked reset appears to have been lost or overridden by the later system-side recalculation.
Could you please review the account logs for:
- the exact time my banked reset was consumed;
- my weekly usage before and after the reset;
- the change of my weekly reset date from September 16 to September 12;
- any automatic/global/account-level reset or usage-window recalculation that occurred afterward;
- whether the consumed banked reset should be restored because its effect was superseded by that system-side change.
I can provide screenshots of my current Usage page and any earlier screenshots showing the previous September 15 reset date.
I am specifically requesting an investigation of a suspected incorrectly applied banked reset, not a courtesy reset.
Thank you.
What steps can reproduce the bug?
Feedback ID: 01a0201d-630a-7c31-8a9e-3d57c7a88f42
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Sep 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
a44235906-lab commentedon Sep 16, 2026
Additional diagnostic evidence from another Windows desktop occurrence on 2026-09-10 (Asia/Seoul, UTC+9). I am adding a transaction failure and history mismatch to this related report; I cannot confirm that both reports have the same root cause.
Environment: Codex desktop 26.901.6511.0, Windows, ChatGPT Pro. Two separately subscribed accounts were used on the same PC, with multiple local tasks. The account distinction below is preserved; old session quota events alone do not identify which account served each response.
For the account with the missing banked reset:
POST /wham/rate-limit-reset-credits/consume -> HTTP 503; upstream connect error or disconnect/reset before headers; connection terminationAn HTTP 503 does not establish whether the backend committed a redemption, and an unchanged weekly percentage alone does not exclude a successful refresh of another eligible window. Please correlate the failed consume request with the grant/redemption ledger, both eligible usage windows, history rendering, and any subsequent reset-window correction or rollback. Please also investigate whether account switching/concurrent desktop tasks can display or apply inconsistent window state; causation is not established.
The original timestamps and screenshots are already supplied through private Support cases. Account identifiers and raw screenshots are deliberately omitted here. The requested technical outcome is a consistent, auditable redemption result and correction of any verified lost benefit. Individual restitution requests remain with Support.
johnconnor2020 commentedon Oct 7, 2026
I have the same issue, Tibo issued reset this morning and I opened Codex with only 94% reset?!