Terra/Sol/Astra repeatedly hits “Selected model is at capacity. Please try a different model.” in Codex

I am using the Windows Codex Desktop app, version 26.901.41600, and working on a remote project with Codex CLI 0.153.4 under a Pro 20x subscription.

For the past two days, my sessions have consistently failed with the following error:

“Selected model is at capacity. Please try a different model.”

This occurs regardless of which model I select, including Terra, Sol, and Astra. The issue is persistent rather than intermittent and is severely disrupting my work.

Could you please help look into why this is happening and advise on how I can resolve it?

Screenshot of the Codex Desktop app with Codex CLI shown in the bottom panel:

Feedback ID:
01a05cc1-8028-7560-a03b-a29de5e79b30

The error is probably accurate and reflects load management restrictions.

The massive popularity of Astra is probably to blame :wink:

This has been raised before and resolved once capacity and load management issues have been resolved.

It is extremely disappointing to be on a Pro 20x subscription and still be unable to use even Terra due to persistent capacity errors :cry:

100%, message Tibo on X publicly and see if you can arrange a Reset :wink:

The entire community supports you “We like it” :smiling_face_with_sunglasses:

same with you, how to solve it?

same here. this means global incident..

Codex has limit for all the modele but it should not have limit on legacy old model why i cant work anymore . this is not fair for student who pay 23 euro

how to fix it,I change all kind of modles,but not useful

Same problem here. I’ve raised it across every channel, but nobody has gotten back to me, and it doesn’t seem like they’re going to fix it

I’m in the same situation; it’s really tough.

Same situation, oh my god

you are not the only 20x pro that be treated like this,almost all model wil end with “Selected model is at capacity. Please try a different model.” only can work for a few minutes and then stop again time by time.i have nothing to say with it.

It could be a concurrency limitation. Try keeping only one dialog running and see if that works.

same with you, how to solve it?

Same. It’s been two days, really make me exhausted. Spent 200 dollars and only got this kind of treatment.

Guess its ip problem again,I cant work remote

don’t know when this issue will be solved. money & time wasting…