openai / openai/codex

[Pro 20x] Weekly reset date moved Sep 15 -> Sep 19 with no reset used; anchor re-set to Sep 12 18:54 AEST (Sep 9 incident?)

Open
#45,236 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What issue are you seeing?

Pro 20x account. Weekly Work/Codex reset date moved from Sep 15, 2026 ~11:00 AM AEST to Sep 19, 2026 6:54 PM AEST with no user action. No banked reset applied (2 credits still available), no instant reset purchased, no plan change, account not shared. The new date implies the weekly anchor was re-set to Sep 12, 2026 ~6:54 PM AEST (08:54 UTC), a time with no Work/Codex activity on the account.

Same pattern as #44663 and #44210, same week.

Timeline (Australia/Melbourne, UTC+10)

  • Sep 8, 2026: upgraded Plus -> Pro 5x -> Pro 20x, all the same day. Work/Codex allowance starts.
  • Sep 8 to 12: Settings > Usage shows weekly reset Sep 15 ~11:00 AM, i.e. 7 days after first Work/Codex use following the upgrade, as documented.
  • Sep 9, 2026: OpenAI status page incident "unexpected usage limit resets" (marked resolved 17:54 UTC).
  • Sep 12, 2026 ~6:54 PM: no activity. No reset purchased, no banked reset used, no plan change.
  • Sep 13, 2026: Settings > Usage now shows Resets Sep 19, 2026, 6:54 PM. Work/Codex at 100%. 2 reset credits still available.

Net effect: four extra days of lockout on an already exhausted allowance.

What support said

Support case 14983099 (email, AI-assisted responder). It confirmed 2 reset credits remain on the account, computed the new anchor as "around Sep 12 at ~6:54 PM", and stated that "some automatic resets apply directly and won't show as a saved reset". It has not been able to say what event created the Sep 12 anchor and has not escalated to a human.

What steps can reproduce the bug?

Not user reproducible; this is a server side quota state change.

  1. Upgrade to Pro 20x on Sep 8, 2026 and use Work/Codex.
  2. Observe Settings > Usage reset date of Sep 15 ~11:00 AM AEST through Sep 12.
  3. Take no reset action (no instant reset purchase, no banked reset; both credits remain).
  4. On Sep 13, observe reset date now Sep 19, 2026 6:54 PM AEST, with Work/Codex at 100%.
What is the expected behavior?

Weekly window anchored to the first Work/Codex request after the Sep 8 upgrade, so a reset on Sep 15. The anchor should not move without a reset event on the account.

Ask

A server side check of the usage/reset ledger for this account around Sep 12, 2026 08:54 UTC: what applied that anchor? If it was an automatic or global reset during or after the Sep 9 incident, it did not benefit the account; it moved the reset later. Restoring the Sep 15 window or adding a reset credit would make it whole.

Environment

  • ChatGPT Pro 20x
  • ChatGPT desktop app on Windows 11, plus web and Android; same reset date shown on all three
  • Timezone Australia/Melbourne
  • Screenshots of Settings > Usage and transaction history are attached to support case 14983099 and available on request.
Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the usage/reset ledger around Sep 12, 2026 08:54 UTC and the related reports #44663 and #44210. Done means identifying the event that moved the anchor and determining whether the Sep 15 window or a reset credit should be restored.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.