Weekly reset timestamp appears stale after Sep 7 global Codex reset #44201

What issue are you seeing?

After the September 7, 2026 automatic/global Codex reset, my weekly allowance was refreshed, but the weekly reset timestamp shown in Usage appears to have remained on the pre-global-reset schedule instead of being reconciled to the new allowance state.

Current Usage UI (Asia/Shanghai, UTC+8) shows:

• Weekly usage remaining: 4%
• Next reset: 2026-09-13 13:52

The important point is that Sep 13 13:52 was already the scheduled weekly reset time before the recent global reset. The global reset refreshed usage, but this displayed weekly reset anchor appears unchanged.

OpenAI's current Help Center confirms that an automatic/global reset was provided to Plus, Pro and Business users on Sep 7, 2026 and that an automatic/global reset refreshes eligible usage limits. The documentation explicitly says a banked reset changes the weekly reset date, but it does not clearly state whether a global reset should preserve or re-anchor the weekly reset date.

Because the allowance state changed while the displayed reset timestamp apparently did not, I cannot tell whether this is:

1. intended behavior for automatic/global resets,
2. a stale Usage UI timestamp,
3. a backend reset_at / allowance reconciliation mismatch, or
4. a partial reset-event application.

Steps / observed sequence

1. Have an active paid ChatGPT plan with an existing weekly Codex usage window and note the next weekly reset timestamp.
2. The Sep 7, 2026 automatic/global reset is applied to the account.
3. Observe that weekly usage is refreshed.
4. Use Codex normally after the global reset.
5. Re-open Settings → Usage.
6. Observe that the weekly reset timestamp is still the same timestamp that was shown before the global reset (in this case Sep 13, 2026 13:52 Asia/Shanghai).

Expected behavior

Please clarify and make the state internally consistent:

• If a global reset starts/re-anchors a fresh weekly window, the displayed reset_at should be updated accordingly.
• If a global reset intentionally refreshes allowance without changing the existing weekly reset anchor, the UI/help documentation should state that explicitly.
• If the account received only a partial reset event, Usage should expose enough event history to show what changed and when.

Why this looks related to existing reset-state bugs

There are several related reports, but I did not find one matching this exact Sep 7 symptom (allowance refreshed by a global reset while the old weekly reset timestamp appears to remain):

• Unexpected weekly usage reset overwrites active Codex window and moves reset date — third occurrence #38332 — unsolicited weekly reset moved the reset date to a new seven-day window.
• Bug: Weekly quota not reset in July 14 global reset (8M users milestone) #33344 — global reset was not applied and quota/reset date both remained unchanged.
• [Bug] Free reset changed weekly reset_at without restoring allowance #34874 — possible partial reset where reset_at changed without allowance replenishment.
• Codex usage limits desync between web Analytics and macOS app #23192 / Codex works in browser but desktop app as well as cli fail to connect to account #34159 — usage/reset timestamp desynchronization across surfaces.
• Global resets can nullify banked-reset value with only hours of notice, undermining quota trust for heavy users #43643 — Sep 7/8 global reset overwriting recently redeemed banked-reset value.

This report is specifically about the opposite/inconsistent combination: allowance refresh observed, but the pre-reset weekly reset timestamp appears to persist.

Environment / evidence

• Product surface: ChatGPT / Codex Settings → Usage
• Locale/time zone: Chinese UI, Asia/Shanghai (UTC+8)
• Observed on: 2026-09-10
• Screenshot available showing Weekly usage limit, 4% remaining, Resets 2026-09-13 13:52.

I can provide additional account-specific timing or diagnostics privately if needed. Please verify the server-side reset-event ledger and reset_at value for the Sep 7 global reset.