Repository navigation
Selected model is at capacity #19583
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.422.30944
What subscription do you have?
Pro 200 USD
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Message sayung Selected model is at capacity, even though my token limits are only used 10% of my plan.
I’ve had a session work to test an electorn app’s interfaces and log each window’s errors, and suggest optimization improvements based on log outputs and delays, it Worked for 3h 9m 39s, then stopped suddenly saying Selected model is at capacity.
Then every conversation with GPT 5.5 xhigh on a Pro 200 USD account kept saying the same thing, so i was no longer able to use this model so i had to switch back to 5.4 xhigh to continue my work.
Is it an issue from my side or is this an OpenAI issue? I’ts been2 hours and still the same issue.
What steps can reproduce the bug?
Running 5.5 xhigh on a long running simulation, testing and documentation session (3 hours +).
What is the expected behavior?
Continue working until limit exhaustion or finalization
Additional information
No response
Activity
github-actions commentedon Apr 25, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
abduhman-star commentedon Apr 25, 2026
The issue you mentioned is in CLI, but my issue is with codex, also i'm on the highest tier plan.
abduhman-star commentedon May 9, 2026
This occured for a while, then it stopped.
LogiHard commentedon May 12, 2026
me too
tairerez commentedon May 12, 2026
Me too
etraut-openai commentedon May 12, 2026
If you receive this message, it does not mean that you are being rate limited or are out of usage. It means that we are running low on capacity to serve this model in your region.
alexsolich-cpu commentedon May 12, 2026
me too
Mo1sson commentedon May 12, 2026
me too
24 remaining items
mylee04 commentedon Jun 16, 2026
I got this too, please fix it!
maxim-karnaukh commentedon Jun 16, 2026
Same issue
cowwoc commentedon Jun 16, 2026
Please upvote the issue instead of adding more comments; otherwise, it spams everyone else.
HarelPerry commentedon Jun 16, 2026
+1 codex
guidejosephine commentedon Jun 16, 2026
guidejosephine commentedon Jun 16, 2026
me too
hockor commentedon Jun 16, 2026
me too
chaprot commentedon Jun 16, 2026
+1. Switched to GPT 5.4, working fine now.
VinguardCP commentedon Jun 16, 2026
me too in 5.5, but I switched to GPT 5.4 and worked fine with any problem
gabrieldeoliveira96 commentedon Jun 16, 2026
eu também
artamaral commentedon Jun 16, 2026
me too in 5.5;
5.4 does not show the problem and it is much faster at the moment. not felling any diff between both.
JVictor-Top commentedon Jun 16, 2026
me too
etraut-openai commentedon Jun 16, 2026
This issue has been mitigated.
I'm going to close and lock this issue because it's quite old. If you see this problem again, please open a new issue.