Codex Weekly Usage Reset succeeded, but requests are intermittently blocked by an incorrect usage limit

Start by reproducing the issue's reset-and-repeat steps, then compare the Usage page's remaining percentage and reset timestamp with the intermittent request responses. Done means requests remain accepted while usage is below exhaustion and the displayed reset state matches the limit enforced for requests.

What version of the Codex App are you using (From “About Codex” dialog)?

26.730.61639

What subscription do you have?

chatgpt plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Hello OpenAI Support,

I am experiencing what appears to be a Codex usage-limit synchronization issue after using the official Reset Weekly Usage feature.

Environment

ChatGPT plan: Plus
Codex: ChatGPT Windows desktop app / Codex
ChatGPT Web shows the same usage information
Date: August 6, 2026

What happened

On August 6, I used the official Reset Weekly Usage feature.
The weekly usage was successfully reset to 100% remaining.
After using Codex for a short period, the Usage page now shows 96% remaining.
The Usage page shows the next reset time as August 13, 2026 at 15:52.
However, Codex intermittently rejects requests with the following message:

"You've reached your usage limit. Upgrade your plan or purchase additional credits to continue, or try again after Aug 13, 2026 at 15:52."

This does not appear to be an actual exhaustion of my weekly quota because the Usage page still shows 96% remaining.

More importantly, the behavior is intermittent even within the same Codex conversation.

For example, I tested several extremely simple requests:

hello → succeeded
hello → succeeded
hello → rejected with "You've reached your usage limit"

Therefore, this does not appear to be related to the size or complexity of the project/task.

I also tried signing out and signing back in, but the issue persists.

Both the Windows desktop app and ChatGPT Web show 96% weekly usage remaining, so this does not appear to be a local desktop-client cache issue.

Expected behavior

Since my official Weekly Usage Reset succeeded and the Usage page currently shows 96% remaining, Codex requests should continue to work until the weekly allowance is actually exhausted.

Actual behavior

Codex intermittently treats my account as if the weekly allowance were completely exhausted and blocks requests until the next weekly reset time, even though the Usage page reports 96% remaining.

Interestingly, the incorrect limit error uses the exact same reset timestamp shown on the Usage page (Aug 13 at 15:52). This suggests that the new weekly usage window was created correctly, but some server-side quota/rate-limit state may not have synchronized correctly after the manual reset.

Could you please check the server-side Codex quota/rate-limit state for my account, particularly whether the official Weekly Usage Reset was correctly propagated to all relevant quota/rate-limit systems?

I have screenshots showing:

Weekly Usage: 96% remaining
Next reset: Aug 13, 2026 at 15:52
Successful hello requests
A subsequent hello request in the same conversation being rejected due to the usage limit

Thank you.

What steps can reproduce the bug?

Open ChatGPT and go to Codex.
Use the official Reset Weekly Usage feature to reset the weekly usage limit.
Confirm that Weekly Usage is successfully reset to 100% remaining.
Use Codex normally for a short period. The Usage page currently shows 96% remaining.
Start a Codex conversation and send a simple request such as hello.
Repeat the same simple request several times.
Some requests succeed normally, but another request is suddenly rejected with: "You've reached your usage limit... try again after Aug 13, 2026 at 15:52."
Check the Usage page again. It still shows 96% remaining, with the next reset scheduled for Aug 13, 2026 at 15:52.
The issue occurs even though there is still 96% weekly usage remaining, and it can happen intermittently within the same Codex conversation.
Signing out and signing back in does not resolve the issue.

What is the expected behavior?

No response

Additional information

No response