Why did my Codex limit not reset?
Run a Codex reset failed checklist when a Codex reset signal did not match your account: Codex rollout lag, plan scope, 5-hour vs Codex weekly.
This is an unofficial tracker. It is not affiliated with OpenAI. Codex is a product/trademark of OpenAI. Probability scores are public-signal heuristics, not authoritative announcements or certainty.
Check these 5 things
First check the reset time shown in your Codex usage UI. Then verify your plan/workspace, compare 5-hour versus weekly windows, distinguish banked reset from automatic reset, and account for timezone or rollout lag.
Evidence checklist
Before asking support or comparing with other users, capture: usage page screenshot, plan tier, remaining percentage, next reset timestamp, timezone, whether a banked reset button is visible, and what changed after the public signal.
What not to do
Do not redeem a banked reset just because a public signal said so. Do not share screenshots that include your email, API key, or workspace name with strangers. Do not assume a Discord screenshot proves a global reset. Do not paste Codex login credentials into any third-party tool that claims to "check your reset," including any tool other than your own Codex UI and the Codex Reset Radar alert form. If you want a heads-up the next time the radar logs a strong signal, subscribe at Codex reset alerts. For the assumptions behind our heuristics, see Methodology.
Why Your Codex Limit Looks Stuck: A Step-by-Step Troubleshoot
The reset signal you saw on Reddit, the dashboard, or our Codex reset history page describes a public pattern. It does not describe your specific account. Before you assume Codex is broken, walk through this checklist. It is built from the failure modes we see most often in user reports: rollout lag, plan-scope mismatch, window confusion, and banked-reset misreading.
Step-by-step: what to check, in this order
- Confirm what your Codex usage UI shows right now. Open the Codex usage panel and read three numbers: the percentage remaining, the next reset timestamp, and whether a "use banked reset" button is visible. Your UI is the only authoritative source. If the timestamp already moved past the public signal time and the percentage has not changed, you are not stuck, you are watching rollout lag. That is the most common cause.
- Confirm your plan and workspace scope. A reset announcement may apply to ChatGPT Plus, ChatGPT Pro, ChatGPT Work, or ChatGPT Team. It may apply only to a single workspace inside a team account, or only to the default workspace. If your account is on a different tier or a separate workspace, the reset never applied to you. Verify in your Codex account header or billing page before you compare notes with anyone else.
- Decide which window you are watching. Codex has two reset windows: the short 5-hour usage window and the longer weekly quota. A "reset" can refer to either. If your weekly quota is already exhausted, a 5-hour reset will not help. Conversely, a weekly reset will not refill a 5-hour window that ran out mid-day. Read 5-hour vs weekly Codex reset for the visual breakdown.
- Decide whether a banked reset is on the table. A banked reset is a manual button that you choose to spend; it is not automatic. If your usage UI offers the button, it is a separate lever that does not trigger from public signals. If you used a banked reset earlier in the cycle, it may already be spent, which can make a later signal look like a "failed reset." Read how Codex banked resets work before you spend another.
- Account for timezone and rollout lag. Public signals are usually captured in UTC. Your Codex UI may show a different timezone, so an "8:00 reset" you expected at 4 PM your time can look late when it is actually on schedule. Add one to six hours of grace for rollout. If the next reset timestamp in your UI has not yet been crossed, the reset has not failed, you are simply early.
- Capture the evidence. Before you compare with another user or open a bug report, screenshot: the usage page with remaining percentage, your plan tier, the next reset timestamp, the timezone shown, the presence or absence of the banked reset button, and the post-signal state. Without this, every report you file looks identical to a normal late rollout, and you will be told to wait.
- Decide: wait, or report. If your UI timestamp has not yet crossed the signal time, wait at least six hours. If it has crossed, and your percentage has not moved, and your plan and workspace match the signal, you have a real anomaly. Report it with the evidence above.
Plan-scope at a glance
| Plan tier | Typical reset trigger | Does a public signal apply automatically? | Banked reset available? |
|---|---|---|---|
| ChatGPT Plus | 5-hour + weekly | Often, but rollout can lag by plan | Yes, usually once per cycle |
| ChatGPT Pro | 5-hour + weekly | Yes, usually faster rollout | Yes, higher cap |
| ChatGPT Work | Per-workspace | Only for the listed workspace | Depends on admin policy |
| ChatGPT Team | Per-workspace | Only for the listed workspace | Depends on admin policy |
This table is heuristic, not official. Your plan row is the one that matches your billing page, not the one someone else claims they are on. If you are on a team plan and the signal mentioned a default workspace only, you may need to ask your admin before assuming a missed reset is a bug.
When to wait, and when to report a bug
Wait when any of these is true: the next reset timestamp in your UI has not yet been reached; your plan or workspace does not match the signal; you have an unused banked reset that resolves the issue; or the signal is less than six hours old. These are all expected conditions, not bugs.
Report when all of these are true: your UI timestamp has crossed the signal time by more than six hours; your plan and workspace match the signal; your percentage has not moved; the banked reset button is absent or already spent; and you have screenshots. With that evidence, a support ticket will be processed on substance, not dismissed as user confusion.
A failed reset is rarely an OpenAI outage. It is almost always a mismatch between a public signal and the slice of Codex your account happens to sit in. Work through the seven steps above in order, and most "stuck" limits resolve themselves.
Two adjacent reads if the limit that looks stuck is not Codex at all: how a ChatGPT rate limit reset works covers the chat-window throttle, a separate clock from Codex quota; and why no GPT-5 reset tracker can see your quota explains what public tracker signals can and cannot tell you.
Want the next strong Codex reset signal?
Get an email when the radar logs a stronger public reset signal.
Get reset alerts →Why did my Codex limit not reset? FAQ
Why did other Codex users reset but I did not?
Public reset signals can roll out unevenly or apply to specific plans, workspaces, or account states. Your Codex usage UI remains the source of truth.
Does a failed reset mean Codex is broken?
Not necessarily. It may be rollout lag, a different quota window, weekly limit depletion, or banked reset confusion. Collect UI evidence before comparing with others.
Should I enter credentials to check my reset?
No. Codex Reset Radar never needs OpenAI login details, API keys, cookies, passwords, or tokens. Check quota only inside your own Codex UI.
Which window should I check first: the 5-hour or the weekly one?
Codex runs a short 5-hour usage window and a separate weekly quota. A 5-hour reset will not refill an exhausted weekly quota, and a weekly reset will not restore a 5-hour window that ran out mid-day. Separate the two windows before reporting a failed reset.
Does a reset signal apply to my whole team workspace?
Not necessarily. On ChatGPT Work and Team plans a reset can apply per workspace, sometimes only the default workspace named in the signal. Confirm your plan tier and workspace in your Codex account header or billing page before comparing with other users.