[Bug] Free reset changed weekly reset_at without restoring allowance
Environment
- Codex for Windows 26.715.12143
- ChatGPT Plus
- Windows 11
- Not model-specific
Issue
A free Codex usage reset may have advanced the backend weekly reset_at timestamp without applying the corresponding weekly allowance replenishment.
Observed sequence:
- Jul 18, 2026: next reset showed Jul 24.
- Jul 19: it changed to Jul 25.
- Jul 20: it changed to Jul 26.
- During this period, the weekly allowance did not replenish.
- Codex remained usable and usage continued to be deducted.
- Refreshing, signing out/in, changing browsers, devices, networks, and VPN settings did not correct the day-level change.
- A later free reset restored the allowance to 100%.
- Two remaining manual Full reset credits were unchanged, so I did not trigger that restoration manually.
- After normal usage, the page showed a new reset time of Jul 29, 2026 at 10:26.
Suspected behavior
An earlier free reset may have updated the weekly window and reset_at, but failed to apply the allowance restoration. A later free reset appears to have applied both.
This is a hypothesis requiring backend verification.
Expected behavior
A free reset should update the reset window and replenish the allowance consistently, or leave both unchanged.
Diagnostics
Feedback ID: no-active-thread-019f8d3c-1f1c-7f12-9f92-e62e00bd213e
Private Support case with sanitized HAR and account evidence: 11775963
I will not upload the HAR publicly.
Please check whether free/special reset events can update reset_at independently from allowance restoration, causing a partial failure.
Related to #9508, but this report concerns a possible partial reset failure.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Would it be possible to just stop doing free resets? Because right now I got scammed of a week. And it I got this error many other people also got it. So your free reset are actually working against us
I am experiencing a very similar issue.
In my case, the free reset appears to have changed the weekly reset_at timestamp while the allowance was not replenished.
The issue was reported under:
Support Case: 11775963
This may indicate that free reset events can partially fail: updating the weekly window without correctly restoring the allowance.
Please check whether multiple users are affected.