Selected model is at capacity

Resolved 💬 44 comments Opened Apr 25, 2026 by abduhman-star Closed Jun 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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_

View original on GitHub ↗

44 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19579

Powered by Codex Action

abduhman-star · 2 months ago
Potential duplicates detected. Please review them and close your issue if it is a duplicate. * Selected model is at capacity. Please try a different model. #19579 _Powered by Codex Action_

The issue you mentioned is in CLI, but my issue is with codex, also i'm on the highest tier plan.

abduhman-star · 2 months ago

This occured for a while, then it stopped.

LogiHard · 2 months ago

me too

tairerez · 2 months ago

Me too

etraut-openai contributor · 2 months ago

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 · 2 months ago

me too

Mo1sson · 2 months ago

me too

jalapenopeppers · 1 month ago

Happening for me on 5/26:

  • GPT-5.5 on high
  • VSCode Codex extension v26.513.21555
BaekSe · 1 month ago

same on 6/9

  • GPT-5.5 Xhigh
  • Codex Desktop osx
gorillakelvin · 1 month ago

same at 6/9

  • GPT-5.5 High
  • Codex Desktop Window
herbyhabi · 1 month ago

I've encountered this problem too, and I'd like to ask how to solve it effectively. Will it just get better after waiting for a while?

cowwoc · 1 month ago

This issue isn't resolved. Codex CLI should retry with a backoff instead of aborting what it was working on...

constantins2001 · 1 month ago
This issue isn't resolved. Codex CLI should retry with a backoff instead of aborting what it was working on...

The Codex app sadly also doesn't retry, but I guess this is a measure to shed load. Still quite annoying.

liyang53719 · 1 month ago

Pro 100 USD
ubuntu22.04 vsode+codex
GPT-5.5 High
Selected model is at capacity. Please try a different model.

mauri3112 · 1 month ago

I'm also experienced this today...

q587p · 1 month ago

Same here. Not fun at all!

DestinyOfLove · 1 month ago

Happen on me today. In both remote session and local session. BTW, it might work for just 2mins but stop sliently again.
Pro 200 USD
Linux & Macos
GPT-5.5 high
Selected model is at capacity. Please try a different model.

DestinyOfLove · 1 month ago

Damn!!! GPT-5.5-xhigh also be declined too.

clunizzi · 1 month ago

me too
Pro 5x
Linux Debian
GPT-5.5 High
Selected model is at capacity. Please try a different model.

Switched to Medium it seems going. But I'm a little bit disappointed, I've just subscribed the Pro plan guys

Edit after 13 minutes: gpt-5.5 medium is stuck working:
Falling back from WebSockets to HTTPS transport. stream disconnected before completion: An error
occurred while processing your request. You can retry your request, or contact us through our help
center at help.openai.com if the error persists. Please include the request ID 922b2bc0-65f7-45d4-
b24f-b1a1ba30ab54 in your message.

KeiraX · 1 month ago

I ran into this problem today as well. has anyone managed to solve it?
5.5-xhigh 、codex app、pro-20x

Jordan-Murray · 1 month ago

Also me, 5.5 x-high fast, codex windows app, pro-20x

LemonCANDY42 · 1 month ago

Same here, 5.5 xhigh/high, codex mac app, pro-20x

ZenoBell · 1 month ago

same issue multiple times per day , please fix it.

Flavie404 · 1 month ago

same, they might have to much success with anthropic drama

eric-xdp · 1 month ago

me too

uuukio · 1 month ago

me too

fehlin · 1 month ago

Same issue

evgenijascott2000-hub · 1 month ago

me too

duchian · 1 month ago

same for me

liuyan123456875274385 · 1 month ago

me too

mylee04 · 1 month ago

I got this too, please fix it!

maxim-karnaukh · 1 month ago

Same issue

cowwoc · 1 month ago

Please upvote the issue instead of adding more comments; otherwise, it spams everyone else.

HarelPerry · 1 month ago

+1 codex

guidejosephine · 1 month ago
### 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_
guidejosephine · 1 month ago

me too

hockor · 1 month ago

me too

chaprot · 1 month ago

+1. Switched to GPT 5.4, working fine now.

VinguardCP · 1 month ago

me too in 5.5, but I switched to GPT 5.4 and worked fine with any problem

gabrieldeoliveira96 · 1 month ago

eu também

artamaral · 1 month ago

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 · 1 month ago

me too

etraut-openai contributor · 1 month ago

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.