RAP Sheet home
Install the bug reporting skill
Its theme's rank, 14 days: 4 on the Codex sheet
31 people reported

All time, since Sep 16, including 14 thumbs-up on GitHub.

Model at capacity errors

“Failures occur while most of my weekly usage is still remaining — not a usage-limit or quota problem.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/13312/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 4 reports and thumbs-up in the last 7 days and 2 the week before, down from 15 a week at the mid-September peak.

Turns fail with "Selected model is at capacity" despite usage remaining. Turns end with server_overloaded on every model tried, while weekly usage and credits remain and rate_limit_reached_type is null; another account on the same machine works.

Is this your bug?

File my report
Where
Codex turns
Error text
Selected model is at capacity. Please try a different model.
Versions
0.153.4 to 26.1027.61615
Platforms
macOS, Web, Windows
How bad
Stops work: a core feature can't be used. Some reports say it blocks them completely.

Part of: Model at capacity errors24 bugs

  1. Model at capacity errors127 people
  2. Model at capacity error34 people
  3. Model at capacity errors40 people
  4. Model at capacity error14 people
  5. Model at capacity errors15 people
  6. Model at capacity errors9 people
  7. Model at capacity error10 people
  8. Tasks interrupted by repeated "Selected model is at capacity" errors and reconnects6 people
  9. Existing long conversations fail with model-at-capacity error4 people
  10. Model at capacity interruptions7 people
Show all 23Show only the largest 10
  1. Model at capacity error5 people
  2. Model at capacity errors3 people
  3. No retry on capacity error2 people
  4. Selected model at capacity4 people
  5. At-capacity and stream disconnects3 people
  6. Model at capacity error3 people
  7. Model at capacity errors4 people
  8. Model at capacity errors2 people
  9. Sol model at capacity2 people
  10. Model at capacity error3 people
  11. Model at capacity error2 people
  12. Spurious model capacity error7 people
  13. Model at capacity errors7 people

Original reports19, newest first

  1. Account-specific server_overloaded while another account works in the same HPC environmentOn GitHub#59322
  2. Persistent "Selected model is at capacity" (server_overloaded) for weeks on single tasks across all models — Paid account stuckOn the forum#1412351
  3. Persistent "Selected model is at capacity" (server_overloaded) for weeks on single tasks across all models despite unused quotaOn GitHub#59099
  4. Pro 20x: Astra/Sol Ultra report capacity across fresh Codex CLI and empty Desktop chats despite available quotaOn GitHub#58875
  5. Pro account: 'Selected model is at capacity' on every model for 7 days — has the team seen this account-level pattern?On GitHub Discussions#57675
  6. Persistent intermittent "Selected model is at capacity" (server_overloaded) for ~1 month — model-agnostic, Pro 20x with usage remainingOn GitHub#55900
  7. Persistent "Selected model is at capacity" error despite remaining quotaOn GitHub#55832
  8. Account-specific server_overloaded / capacity on Pro despite usage remaining (thread 01a1337b-ddfb-7013-ba44-2716c02d2789)On GitHub#53555
  9. Codex macOS: repeated server_overloaded on Pro with usage remaining; US residential egress did not helpOn GitHub#53307
  10. Selected model is at capacity. Please try a different model.On GitHub#46956
Show all 19Show only the newest 10
  1. Codex Desktop repeatedly shows “Selected model is at capacity” only on my Pro accountOn GitHub#46724
  2. Account-scoped "Selected model is at capacity" on a Pro account since Sept 14 - cross-over test shows it follows the account, not the machine or networkOn GitHub#46231
  3. Pro account: "Selected model is at capacity" on every model, every surface, ~10 daysOn GitHub#46214
  4. Persistent "Selected model is at capacity" error prevents Codex usageOn GitHub#46205
  5. Account-level "Selected model is at capacity" on 100% of requests across all models (Pro plan)On GitHub#46185
  6. Selected model is at capacityOn GitHub#46142
  7. Account-specific server_is_overloaded on GPT-5.6 Sol: one Plus account fails while two other Plus accounts work on same machine/networkOn GitHub#46133
  8. CLI 0.154.0: "at capacity" since 11 Sep despite 5h 100% / weekly 80%On GitHub#45909
  9. CLI 0.154.0: "at capacity" since 11 Sep despite 5h 100% / weekly 80%On GitHub#45892

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.

Claim a tool