All 4 of my paid Business Standard seats missed the Oct 2 global reset, while Pro 500 was fixed

ChatGPT Bugs
,
1

Hi everyone,

I’m posting this because at this point I’m genuinely frustrated with how ChatGPT Business Standard users are being handled in this reset.

Tibo announced the Oct 2 global reset for “all paid ChatGPT accounts” and later said that the reset had fully propagated.

I have four paid ChatGPT Business Standard seats, across my Business setup, and not a single one of them received the reset. The Codex usage and reset times are still exactly where they were before the global reset.

This makes it very hard to believe this is just an isolated account issue.

I’ve also seen Business Premium users receive the reset, while multiple Business Standard users are reporting that they did not. If Business Standard was intentionally excluded, that was never stated in the announcement. The wording was “all paid ChatGPT accounts.”

What makes this more frustrating is what happened with Pro 500. After the main reset, Tibo noticed reports that Pro 500 users had not received it, said he was investigating and would make up for it, and then shortly afterwards confirmed: “All fixed.”

So OpenAI was able to identify another paid cohort that had been missed and correct it. But Business Standard users are still sitting here without the reset, more than a day later.

And this is not the first time this has happened to Business. In July, OpenAI explicitly confirmed that Business workspaces had been “inadvertently omitted” from two Codex hard resets and later issued a corrective Business reset.

I have already opened OpenAI Support case #16341140, but so far I have only received AI-assisted replies instead of an actual investigation.

Could someone from OpenAI please confirm:

  1. Was Business Standard supposed to be included in the Oct 2 reset?
  2. If yes, why are Business Standard seats still missing it after the reset was declared fully propagated?
  3. Since Pro 500 users were given a corrective fix, will the same be done for affected Business Standard users?

If you’re also on Business Standard and did not receive the reset, please reply here. It would be useful to establish how widespread this is.

2

@OpenAI_Support please,the problem that needs to be solved

3

Adding our organization’s confirmation here to help establish the widespread nature of this issue.

We are experiencing the exact same failure across all 3 paid Standard seats in our Business workspace (gptTeam). Not a single seat received the October 2 global reset or any banked credit.

Here is our exact setup and current state:

  • Plan: ChatGPT Business (Team Workspace, Standard Seats)
  • Current Status: Our weekly Codex limit remains completely frozen at ~2% remaining with the unreset countdown (“Resets in 4d”).
  • Client Verified: Tested and confirmed across the latest Windows Desktop app build (26.930.31730, Oct 3 build) and web interfaces.
  • Support Ticket: Logged under Case #16335162.

We share your exact frustration regarding the contrast with Pro 500. When Pro 500 accounts were missed, Tibo acknowledged the reports and resolved it within hours (“All fixed”). Yet Business Standard seats–which represent paying team customers relying on Codex for production development–have been completely ignored for over 40 hours.

To make matters worse, as you pointed out with your Case #16341140, Support’s front-line AI bot has been putting us through an endless checklist loop (demanding everything from exact Org IDs, Workspace UUIDs, client build strings, to live Codex task telemetry links) rather than acknowledging a systemic tenant-level propagation gap.

Just like the July incident where OpenAI admitted Business workspaces were “inadvertently omitted” and had to issue a corrective reset, this is clearly another batch omission where the multi-tenant workspace tables were bypassed by the global script.

Hoping someone from the OpenAI team or @thsottiaux sees this thread and pushes a tenant-wide Corrective Business Reset without forcing every single team to individually battle the AI support gatekeeper.

6

We encountered an issue during the latest global usage reset.

At the time of the global reset, Pro 500, Business Premium, and Business Standard accounts did not receive the usage reset.

After the fix for Pro 500 was announced, we noticed that Business Premium accounts also received the reset.

However, Business Standard users still have not received the usage reset.

Could the OpenAI team please check whether Business Standard accounts were missed during the fix?

Thank you.

7

Can confirm your exact findings. We have 3 paid Business Standard seats in our workspace (gptTeam), and not a single seat received the reset. Our weekly limit is still completely frozen at ~2% remaining with the natural 4-day countdown unchanged.

Your observation about the timeline makes total sense: when Tibo announced “All fixed” for Pro 500, the propagation evidently patched Pro 500 and Business Premium, but completely missed the Business Standard tenant cohort.

To make matters worse, when we reported this with full telemetry under Case #16335162, Support simply sent a boilerplate reply claiming that 0 banked resets doesn’t mean it didn’t apply, and told us to buy Shared Workspace Credits instead of investigating the rollout gap.

This is clearly an acknowledged batch gap in the propagation script, exactly like the July incident where Business was “inadvertently omitted”.

Hoping the OpenAI engineering team sees this and runs the missing sync for Business Standard workspaces as they did for Pro 500 and Premium.

8

I’ve pinged the team to take a look, but I can’t share a timeline yet.

Thanks for raising this, and for confirming that the issue remains after the Pro 500 reset was applied to your accounts.

9

Same here.

Our ChatGPT Business workspace has 8 paid Business Standard seats, and all 8 out of 8 seats did not receive the Oct 2 global usage reset.

We have been actively using Work/Codex, and the usage limits remained unchanged after the announced global reset.

This appears to be affecting entire Business Standard workspaces, not just individual seats.

We have also escalated this to OpenAI Support for investigation.

It would be helpful if the OpenAI team could confirm whether Business Standard was unintentionally missed during the Oct 2 reset or the subsequent fix.

10

I’m on Pro 200, and saw the announcement. But I’m still waiting for the ‘global reset’ also.

11

Business standard too. Did not get the reset.

12

Same here, businness standard, two seats.

13

We are experiencing exactly the same issue on our side. We are using the $25/month Business Standard seats.

Combined with the ongoing issue where Business Standard users are unable to create access tokens, it is becoming difficult not to feel that users on the $25 Business Standard tier are being treated as lower priority.

If Business Standard was not supposed to be included in this reset, that would be understandable if it had been clearly stated from the beginning.

However, the reset was announced as applying to all paid ChatGPT accounts, and despite that, we never received it. This is now having a direct impact on our work.

I do not intend to make this an emotional complaint, but if issues like this continue, we will inevitably have to consider moving to competing products that are more capable and offer better value for money.

At the very least, I would appreciate a clear explanation as to whether Business Standard was intentionally excluded or simply missed during the reset.

14

Any update about this issue? Or are we forced to use a banked reset?

15

I have not received an update, yet, and have no timeline to share.
Sorry, that is not the answer I was hoping for either.

Something you might want to be aware of:

Fingers crossed!

Ps. I’m not an OpenAI employee.

16

It is infuriating to see @OpenAI_Support actively posting in other threads today while completely ghosting this one. This selective silence is an absolute insult to paying business customers.

Let’s call this what it is: blatant, unacceptable discrimination against Business Standard users.

Tibo publicly promised a global reset for “all paid ChatGPT accounts.” When Pro 500 users were missed, he rushed to fix it within hours and tweeted “All fixed.” Business Premium accounts got their reset. Yet Business Standard seats–paying $25/month per seat to run daily production engineering workloads–have been left completely locked out for four full days without a single shred of accountability.

What makes this truly disgraceful is how Support has handled it:

  1. Front-line agents have the audacity to gaslight paying customers with condescending lectures about banked resets while outright ignoring our unreset weekly quotas.
  2. Instead of taking ownership of a verified multi-tenant failure, Support shamelessly tries to upsell us by telling us to buy “Shared Workspace Credits” to regain access to basic service.
  3. And now, official support staff are actively chatting in other forum threads while treating this widespread outage like an invisible elephant in the room.

We are paying customers whose daily engineering operations have been paralyzed. Being treated like second-class citizens while watching support actively dodge this thread is infuriating.

Stop hiding behind AI gatekeepers. Stop ignoring this thread while responding elsewhere. If Business Standard was intentionally excluded, have the courage to state that on the record. If this is a bug, take responsibility, stop the corporate silence, and fix our workspace quotas immediately.

@OpenAI_Support @thsottiaux Stop dodging this issue. We demand an answer.

17

Thanks for the update. Unfortunately, a possible future full reset does not make up for the Oct 2 reset that paid users were supposed to receive.

We now have at least 18 paid Business Standard seats across multiple workspaces reporting the same issue. I still hope the team can apply a corrective reset for the one that was missed.

18

@OpenAI_Support We now have at least 18 paid Business Standard seats across multiple workspaces confirming that the Oct 2 reset was missed. Could the team please review this as a Business Standard cohort issue and apply a corrective reset, as was done for affected cohorts before?

19

@OpenAI_Support same question

20

Brief reminder, this hasn’t been addressed or publicly commented on.

21

While I have no public comment, can you check if you received today’s banked reset?
This should be good to know when pinging the team again.

Maybe wait a few more hours since these resets do take some time to propagate to all accounts.