[Usage accounting] 5-hour and weekly quota state changed together, then reverted (39% → 75% → 38%; Sep 15 → Sep 14 → Sep 15)

What version of the Codex App are you using?

26.905.11957

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows

What issue are you seeing?

I observed a temporary Codex quota/rate-limit state change affecting both the 5-hour and weekly windows at approximately the same time.

The most unusual part is that the weekly quota and reset date first changed substantially, and then later reverted almost exactly to their previous values.

Summary of the observed state transition

State	Weekly remaining	Weekly reset	5-hour window
Before	~39%	Sep 15	Expected reset around ~01:26
Temporary state	~75%	Sep 14	Reset/refreshed early around ~01:12
After reconciliation/reversion	~38%	Sep 15	Refreshed/re-anchored again

In short:

Weekly remaining:
39% → 75% → 38%

Weekly reset date:
Sep 15 → Sep 14 → Sep 15

At the same time, the 5-hour window also changed/reset unexpectedly.

No manual/full reset was intentionally triggered.

The temporary weekly state was also visible on the ChatGPT web usage page, not only in the Codex Windows app.

---

Detailed timeline

All times below are approximate local times on September 10, 2026.

1. Initial state

Before the unexpected change:

• Weekly allowance: approximately 39% remaining
• Weekly reset date: Sep 15
• 5-hour window was showing an expected reset at approximately 01:26

Everything appeared normal at this point.

2. Unexpected change at approximately 01:12

At approximately 01:12, around 14 minutes earlier than the previously displayed 5-hour reset time:

• The 5-hour allowance refreshed/reset early
• Weekly remaining allowance changed from ~39% → ~75%
• Weekly reset date changed from Sep 15 → Sep 14

This was not just a local Codex App display discrepancy: the web usage page showed the same new weekly percentage/state.

I did not manually trigger a quota reset.

3. State later changed back

Afterward, the state changed again:

• Weekly remaining: ~75% → ~38%
• Weekly reset date: Sep 14 → Sep 15
• The 5-hour window also refreshed/re-anchored again

The final weekly state was therefore almost identical to the original state.

So the complete observed transition was:

Initial:
Weekly remaining: ~39%
Weekly reset:     Sep 15
5h reset:         expected ~01:26

        ↓ around 01:12

Temporary:
Weekly remaining: ~75%
Weekly reset:     Sep 14
5h window:        unexpectedly refreshed/reset early

        ↓ later

Final:
Weekly remaining: ~38%
Weekly reset:     Sep 15
5h window:        refreshed/re-anchored again

---

Why this looks like more than a UI percentage glitch

The unusual part is not only that the percentage changed.

At least three pieces of rate-limit state changed together:

1. Weekly remaining allowance: 39% → 75% → 38%
2. Weekly reset date: Sep 15 → Sep 14 → Sep 15
3. 5-hour window: the displayed/reset state changed around the same event, including an apparent refresh roughly 14 minutes before its previously shown reset time.

The weekly change was also reflected on the web usage page, which makes a Codex-App-only stale UI/cache issue seem less likely.

The temporary state also does not look like a normal full reset, because:

• weekly allowance only recovered to approximately 75%, not ~100%;
• the reset date moved from Sep 15 to Sep 14;
• the state later reverted back to approximately its original percentage and reset date.

---

What steps can reproduce the bug?

I cannot reproduce the issue deterministically.

The observed sequence was:

1. Use Codex normally with an active 5-hour and weekly window.
2. Observe:
   • weekly remaining approximately 39%
   • weekly reset Sep 15
   • 5-hour reset expected at approximately 01:26
3. Before that reset time, at approximately 01:12, check usage again.
4. Observe:
   • 5-hour allowance has unexpectedly refreshed/reset;
   • weekly remaining is now approximately 75%;
   • weekly reset has changed to Sep 14.
5. Check the ChatGPT web usage page and observe the same weekly state.
6. Later check usage again.
7. Observe:
   • weekly remaining has returned to approximately 38%;
   • weekly reset has returned to Sep 15;
   • 5-hour state has refreshed/re-anchored again.

No manual reset was intentionally used during this sequence.

---

What is the expected behavior?

I would expect the rate-limit state to remain internally consistent:

• A 5-hour window should reset according to its reported reset timestamp unless the window is intentionally re-anchored.
• Weekly remaining allowance should not temporarily change by ~36 percentage points without attributable usage or an explicit reset.
• The weekly reset date should not temporarily change by one day and then revert.
• If the backend changes the active rate-limit bucket/window or performs usage reconciliation, the resulting state should ideally remain stable and be auditable.

---

Requested engineering investigation

Could the Codex team inspect the server-side rate-limit / usage state for this account around the event and determine:

1. Why did the weekly state transition from ~39% / Sep 15 → ~75% / Sep 14 → ~38% / Sep 15?
2. Why did the 5-hour window appear to refresh around 01:12, when the previously displayed reset time was approximately 01:26?
3. Did the account temporarily resolve to a different rate-limit bucket, quota snapshot, entitlement state, weekly window, or reset anchor?
4. Was a server-side reset or reconciliation operation performed around that time?
5. Why did the temporary state subsequently revert?
6. Which of the two weekly states was considered authoritative by the backend during the transition?

If useful, I can provide screenshots and more precise timestamps for the state transitions.

---

Potentially related issues

This may be related in symptom shape to:

• #44233 — 5-hour allowance appeared restored before its previously reported reset timestamp while weekly allowance/reset state also changed unexpectedly.
• #41220 — meta tracker for abnormal Codex quota / usage-accounting inconsistencies.

My case differs in one particularly useful way for diagnosis:

the altered quota state subsequently reverted.

Specifically:

Weekly remaining:
39% → 75% → 38%

Weekly reset:
Sep 15 → Sep 14 → Sep 15

and the 5-hour window changed during the same sequence.

This may make it possible to distinguish a real quota reset from a transient rate-limit-state / accounting synchronization issue.

---

Additional information

• Codex App: 26.905.11957
• Subscription: ChatGPT Plus
• Platform: Windows
• Date observed: September 10, 2026
• No manual/full quota reset was intentionally triggered.
• The temporary weekly state was also visible on the ChatGPT web usage page.
• The 5-hour and weekly state changes appeared to occur as part of the same event.
• Screenshots / more precise timestamps can be provided if maintainers need them.

No files, tests, or code entry points are named. Start by examining the server-side rate-limit and usage state for the account around the reported timestamps, comparing the Codex Windows app with the ChatGPT web usage page. Done means identifying the authoritative weekly state, the cause of the temporary reversion, and why the 5-hour window was re-anchored.