Missing banked reset after Codex usage limit reset announcement

[William_Lynn]

Hi OpenAI team,

According to Tibo’s announcement on July 15, Codex usage limits were reset for everyone and the reset was supposed to be banked for later use.

I am a ChatGPT Pro subscriber. I can see one Full reset available in my Codex usage settings, but I believe this may be my previous reset credit (it expires on August 13). I cannot confirm that I received the additional reset from the July 15 announcement.

I have:

• restarted Codex
• updated to the latest version

Other users reported receiving the new reset, but I cannot see any additional reset credit in my account.

Could you please check whether my account was credited correctly for the July 15 reset? If it was not applied, could you please add the missing reset?

Account plan: ChatGPT Pro
Region/timezone: UTC+8/UTC+9

Thank you.

[Rawit_Supathanakorn]

Same Issue. My co-worker got reset normally.

[jochenschultz]

UTC +8/+9?

Where is that?

[rpocklin]

@William_Lynn

Account plan: ChatGPT Pro
Region/timezone: UTC+8/UTC+9

Same issue here, no reset

Account plan: ChatGPT Business
Region/timezone: UTC+10

I wonder if it’s because of UTC differences?

[EricGT]

For those who are new to the forum, welcome!

Some of the replies here appear to be better suited to this topic.

ChatGPT Business account did not receive the Codex 8M-user hard reset

Hi everyone, I’m using Codex through a ChatGPT Business workspace, but my account did not receive the recent hard usage-limit reset associated with Codex reaching 8 million users. I have seen reports that other paid-plan users received the reset, but my Codex usage percentage, weekly reset date, and available banked resets have not changed. Could someone clarify the following? Was the 8-million-user reset intended to include ChatGPT Business accounts? Are Business workspace members subject …

If so, pay attention to this reply first

Hey everyone, Based on reviewing some of the tickets. There may be some confusion because there are two types of ChatGPT Codex and ChatGPT Work limit resets:

1. Global or hard resets

These reset the applicable hourly or weekly usage window directly. They do not appear as saved resets. If you continued using ChatGPT Codex or ChatGPT Work afterward, it may not be obvious that the reset was applied because the refreshed window may already show new usage.

2. Saved or banked resets

These appear as available reset credits on the ChatGPT Codex usage page and can be redeemed after reaching a usage limit.

Depending on the campaign, eligible accounts can include Plus, Pro, and ChatGPT Business users.

For Business workspaces, eligibility is evaluated per member, not for the workspace as a whole. Campaign requirements may include:

An active Business membership
A non-usage-based seat
Recent ChatGPT Codex or ChatGPT Work activity
A subscription or workspace membership active before the campaign cutoff
Some campaigns may not target promotional, discounted, newly activated, or other non-standard subscriptions. We reviewed the reported cases individually and, based on the information available, have not found evidence of unexpected behavior.

For saved resets, check: https://chatgpt.com/codex/settings/usage

Before checking, sign in with the affected email, select the correct Plus, Pro, or Business workspace, and make sure you are not viewing a Personal or Free workspace. Saved resets tied to a Business workspace will not appear in the Personal workspace. Thank you!

then possibly this reply in that topic.

Hey everyone, We need your personal details in order to track why you din’t receive the resets. We cannot attain personal information on public forum so am request you to open a support request at support@openai.com (similar to what @EricGT suggested) and please provide your personal account details in that support request. Once you have submitted it with us, share the case ID here so we can track it and investigate. Thank you all for raising this issue here.

If so, then post your case id in that topic, not here. OpenAI may not be tracking updates in this topic.