openai / openai/codex

[Cyber] Codex App: gpt-daybreak-blue-latest rate limited by unrelated org (40M TPM) — regression of #10057

Open
#37,948 9 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

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

Powered by Codex & OWL Version 26.803.81509

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.22621.0 x64

What issue are you seeing?

I am an approved ChatGPT Cyber user and have legitimate access to the Cyber models in Codex.

I am seeing intermittent stream disconnections in the ChatGPT Desktop App (Codex mode) when using gpt-daybreak-blue-latest.

The error is:

stream disconnected before completion: Rate limit reached for gpt-daybreak-blue-latest (for limit gpt-5.6-sol) in organization org-BOvpEHVcDPTe8h4lZnwMO5Ly on tokens per min (TPM): Limit 40000000, Used 40000000, Requested 59984. Please try again in 89ms.

This is not an access/eligibility issue. I am a ChatGPT Cyber-approved user and gpt-daybreak-blue-latest is available to me normally.

The organization shown in this error:

org-BOvpEHVcDPTe8h4lZnwMO5Ly

does NOT belong to my OpenAI account.

I checked my OpenAI Platform organization settings and my actual organization ID is different. I am not a member of the organization referenced in the rate-limit error.

This appears very similar to the previously reported issue:

https://github.com/openai/codex/issues/10057

That issue also reported rate-limit failures against the exact same unrelated organization:

org-BOvpEHVcDPTe8h4lZnwMO5Ly

However, #10057 was closed after the previous service issue was resolved. This appears to be a recurrence/regression, now affecting the current ChatGPT Desktop App / Codex experience while using the Cyber model gpt-daybreak-blue-latest.

The current error indicates:

  • Actual model requested: gpt-daybreak-blue-latest
  • Rate-limit group: gpt-5.6-sol
  • TPM limit: 40,000,000
  • TPM used: 40,000,000
  • Organization being rate-limited: org-BOvpEHVcDPTe8h4lZnwMO5Ly
  • That organization is unrelated to my account
  • I am an approved ChatGPT Cyber user with valid access to this model

It appears that Cyber/Codex requests may be getting rate-limited against a shared or service-side organization/rate-limit bucket rather than the authenticated user's own account context.

Please investigate whether requests to gpt-daybreak-blue-latest from approved ChatGPT Cyber users are incorrectly sharing or inheriting the TPM limit associated with org-BOvpEHVcDPTe8h4lZnwMO5Ly.

What steps can reproduce the bug?

Use gpt-daybreak-blue-latest normally in Codex.

The issue occurs intermittently and may trigger the unrelated-organization TPM rate-limit error during generation.

What is the expected behavior?

Codex requests using gpt-daybreak-blue-latest should complete normally without being rate-limited by an organization that is unrelated to my account.

As an approved ChatGPT Cyber user, I should be able to use the model according to the limits associated with my own account/access.

Additional information

This appears to be related to #10057:

https://github.com/openai/codex/issues/10057

That issue reported the exact same unrelated organization ID:

org-BOvpEHVcDPTe8h4lZnwMO5Ly

In my case, the error occurs with gpt-daybreak-blue-latest and reports:

  • Rate-limit group: gpt-5.6-sol
  • TPM limit: 40,000,000
  • Organization: org-BOvpEHVcDPTe8h4lZnwMO5Ly

This organization does not belong to my OpenAI account.

I am an approved ChatGPT Cyber user and have valid access to the Cyber model.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or code entry point is named. Start by reproducing the intermittent failure in Codex with gpt-daybreak-blue-latest and capture the organization and rate-limit details from the error; done means approved users no longer receive limits from the unrelated organization.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.