Codex rate limit resets disappeared
Open 💬 5 comments Opened Jun 19, 2026 by teabox93-git
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What issue are you seeing?
I had two rate resets available in Coxed, I have not used it and the reset is no longer available (2 resets vanished).
My subscription did not end, however one time payment failed due to card issue. Second payment was succesful.
Still resets vanished and they are not available on codex side.
Is it intended behavior? Why my reset vanished.
What steps can reproduce the bug?
Subscription does not end, but rate limit reset will disappear from the account if payment fails (it seems) or reason was different.
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
<img width="522" height="285" alt="Image" src="https://github.com/user-attachments/assets/e773233f-33cb-49cd-83bb-68024013d3c8" />
you will find it in the menu
No, it was there but now it disappeared
One thing that would make this easier to debug is treating resets as ledger events rather than a display flag. Each reset could have id, window, subscription, payment_state, source, reset_at, expires_at, consumed_at, and revoked_reason fields, with stale/cache/fetch_error state in the UI. Then a failed payment retry or server reconciliation can explain why resets vanished instead of leaving support to infer from account state.
---
_Generated with ax._
Update after checking my local Codex logs/session DB — want to be precise about what I'm actually reporting, since usage accounting itself is presumably correct on OpenAI's side.
no-active-thread-019f649d-9249-7361-968c-64b2e22dc6c6What I'm NOT disputing: the total weekly usage consumed. My local records confirm I genuinely burned significant usage on July 13–14 (via the VS Code extension). I'm not claiming the usage total is wrong.
What I AM reporting — two things that don't depend on how usage was consumed:
~/.codex/sessionsand the local state DB). By July 15 noon, all 3 were gone from the account. Whatever consumed my weekly quota, it should not also silently revoke unused banked reset credits — those are two separate ledger entries.Both of these are entitlement/ledger issues independent of whether my weekly usage total is correct. Given how many similar reports are landing this week (#33017, #33118, #31601, #32311), this looks like a broader reset-bank reconciliation bug rather than anything specific to my usage pattern.
Request: please audit the reset-bank ledger for this account, restore the 3 banked resets that were revoked without being used, and re-apply the July 15 global reset.