Rate limit reached for organization org- on requests per min (RPM): Limit 3000, Used 3000, Requested 1

Resolved 💬 5 comments Opened Jan 28, 2026 by locainin Closed Jan 28, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.92.0

What subscription do you have?

plus

Which model were you using?

gpt-5.2

What platform is your computer?

Linux 6.18.5-arch1-1 x86_64 unknown

What terminal emulator and version are you using (if applicable)?

kitty

What issue are you seeing?

outlines are NOT always active and are inconsistant: [Image#1]
there is also no 3D or shadow effect on the widgets.
this color when something is active also needs to change: [Image #2]

• Context compacted

stream disconnected before completion: Rate limit reached for organization org-<> on tokens per min (TPM): Limit 250000, Used 250000, Requested 57059. Please try again in 13.694s

continue?

stream disconnected before completion: Rate limit reached for
organization org-<> on requests per min
(RPM): Limit 3000, Used 3000, Requested 1. Please try again in
20ms. Visit https://platform.openai.com/account/rate-limits to
learn more.

What steps can reproduce the bug?

Uploaded thread: 019bee19-0b2e-7710-af9d-1abc7c85e586

What is the expected behavior?

I input, get output. Not an error.

Additional information

Maybe this?
Token usage: total=11,014,915 input=9,981,059 (+ 302,021,376 cached) output=1,033,856 (reasoning 573,578)
To continue this session, run...

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 7 months ago

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

  • #10059
  • #10058
  • #10057
  • #10056
  • #10055

Powered by Codex Action

Abhityagi16 · 7 months ago

Came here to report this issue. Switching to gpt 5.2-codex worked for now.

locainin · 7 months ago
Came here to report this issue. Switching to gpt 5.2-codex worked for now.

seems to have worked for me

etraut-openai contributor · 7 months ago

Thanks for reporting. There was a temporary service issue that caused the responses API to incorrectly report rate limit errors when it shouldn't. The issue has been mitigated. Everything should be back to normal now. Apologies for the disruption.

harshrathod0585 · 3 months ago

I’m still encountering issues, and currently, we only have GPT 5.5, 5.4 mini, 5.3 codex, and 5.2. Does anyone have a solution for this? I used our organization’s API key, but it still repeats the same error.