We're currently experiencing high demand, which may cause temporary errors.

Resolved 💬 10 comments Opened Apr 20, 2026 by ShivBackup Closed Apr 21, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.122.0

What subscription do you have?

plus

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 25.2.0 arm64 arm

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

iterm2

What issue are you seeing?

requests are not processing

What steps can reproduce the bug?

any prompt is leading to this issue

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

10 Comments

github-actions[bot] contributor · 3 months ago

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

  • #18682

Powered by Codex Action

fullofcaffeine · 3 months ago

+1

<img width="947" height="55" alt="Image" src="https://github.com/user-attachments/assets/b59b2ca6-d4a4-4793-91eb-186c4dc4b0e7" />

<br/>

EDIT: Thread ID 019d8d1a-7871-7df1-9767-80a86928f499 and 019cb669-5422-7ca0-b7bb-0229699c49bf.

theblackboxinyourhead · 3 months ago

yep same same

CHH-FK · 3 months ago

Same issue here.

desh2608 · 3 months ago

I am also impacted

bandaoshutiao · 3 months ago

:)

et-hicks · 3 months ago

same here

CHH-FK · 3 months ago

The previous issue surfaced by github actions bot tells us that the issue was closed as "not planned" by @etraut-openai .

But whether it's planned or not, it's still affecting our ability to use the service we paid for.
Is it to much to ask that Pro users are allowed to continue working, or at least get some clarity?

GraciousGazelles · 3 months ago

Also experiencing this, unable to send a message with Codex CLI. ChatGPT Web app is working fine.

■ We're currently experiencing high demand, which may cause temporary errors.
etraut-openai contributor · 3 months ago

This incident has been resolved.