Codex "Couldn't reset usage. Please try again": why redeeming a reset fails
The Codex reset error "Couldn't reset usage. Please try again" explained with real GitHub issues: backend failures that waste banked resets, the 80% eligibility rule, and the exact steps to take before you click redeem again.
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.
What the error is
The full message reads Couldn't reset usage. Please try again, and it appears when you redeem a banked reset in the Codex app, on the web usage page, or via /usage in the CLI. It is filed verbatim in openai/codex #44951 and — for banked full resets specifically — in #34249. Community reports show the same failure across the web UI, CLI, and desktop app at once (r/codex thread, Sep 2026), which points at the backend service that grants resets rather than any one client.
The failure that costs you a reset
The worst variant is not the error itself — it is the error combined with a consumed reset. #31601: a user redeemed a reset in the CLI (failed), clicked again in the app (failed again), and burned two of three resets with no quota change. #31606: "Reset failed, did not apply and 1 reset is wasted." #31532: "Codex reset was consumed but usage limit was not reset." Multiple users confirmed the same pattern within hours. If your redeem fails, do not immediately retry — screenshot the usage page with the reset count first, because that count is your evidence.
Check the 80% rule before you blame the bug
Not every "failed" redeem is a bug. OpenAI's Help Center (How resets work in Codex) documents an eligibility rule for banked resets redeemed from Usage settings: at least one covered allowance must have less than 80% remaining. If all covered allowances are at 80% or more, you see "Your usage does not need a reset right now" and the reset stays in your bank. So before retrying: if your bars are healthy, the redeem is legitimately refused — check how to read your /status bars first. If your bars are genuinely low and the redeem still fails, you are in the #31601 pattern.
What to do, in order
One: screenshot the usage page — reset count, both limit bars, timestamp. Two: read the bars: if everything is above 80%, the redeem is correctly refused; save the reset. Three: if bars are low, wait a few minutes and retry once — several of the September 2026 reports describe the backend recovering within the day. Four: if it fails again, stop — every retry risks the consume-without-apply pattern. Five: report with your evidence (GitHub issue or OpenAI support), including timestamps and how many resets disappeared. Six: meanwhile, plan around the natural window instead of gambling more resets — the radar below shows the latest public signal, and alerts can notify you when a stronger one lands.
Failed redeem, or just bad timing?
A refused redeem and a broken redeem look similar in the moment. Use the public timeline as one input — if other users are reporting resets misbehaving at the same time, that leans server-side; if the radar is quiet, lean toward your own eligibility state or a transient blip.
Latest public signal (radar snapshot)
Latest public signal: Tibo on X: banked reset activated — lands in everyone's accounts soon (Nov 12) (2026-11-12) · Public signals logged: 64
Radar monitor
Last radar sweep: 2026-11-22 15:15 UTC. The radar tracks public signals only — it cannot see banked balances, redeem attempts, or any account state.
Public signals are context, not account-level proof. Your Codex usage UI is the source of truth for your banked resets. See the live radar →
Evidence to capture before you retry
Before the second attempt, save: (1) the usage page showing your available reset count, (2) both limit bars with percentages, (3) the exact timestamp and the full error text, (4) which surface you used — app, web, or CLI /usage. This is exactly what makes a GitHub issue or support ticket actionable, and what proves a reset was consumed if the quota never applied.
Sources: real reports behind this error
Every claim on this page traces to a public report. Error text verbatim: #44951, #34249. Reset consumed without applying: #31601, #31606, #31532, #32107. Cross-client failure (web UI + CLI + desktop at once, backend 429): r/codex thread "Reset UI can't display available resets", Sep 2026. Eligibility rule (80% remaining): OpenAI Help Center, "How resets work in Codex". These are community/public reports, not OpenAI documentation, except where noted.
Want the next strong Codex reset signal?
Get an email when the radar logs a stronger public reset signal.
Get reset alerts →Codex "Couldn't reset usage. Please try again": why redeeming a reset fails FAQ
Does "Couldn't reset usage" mean my reset is gone?
Sometimes, unfortunately. Issues #31601, #31606, and #31532 all document resets consumed while the quota never applied. That is why the first move is a screenshot of your reset count — before any retry.
Why does the reset redeem fail when I still have quota left?
Two separate reasons. If your covered allowances all have 80%+ remaining, OpenAI's documented eligibility rule refuses the redeem on purpose (the message differs: "Your usage does not need a reset right now"). If your bars are low and it still fails, that is the server-side failure pattern in #34249 and the September 2026 community reports.
Is it safe to keep clicking "try again"?
No. Each click is a redeem attempt against your banked balance. In #31601 two rapid attempts burned two resets. One careful retry after a pause is the maximum; if it fails again, capture evidence and report.
Is this error related to my weekly reset date?
Indirectly. A successful banked reset restarts your covered usage windows and moves the next refresh time (per the Help Center). A failed one should change nothing — which is why a reset count that drops while the bars stay put is the signature of this bug, worth reporting.
Can Codex Reset Radar redeem or restore my reset?
No. This tracker logs public reset signals only. It has no access to accounts, cannot redeem resets, and will never ask for credentials. Redemption happens only inside OpenAI's own UI.