Experiencing high demand, which may cause temporary errors
Resolved 💬 2 comments Opened Dec 16, 2025 by cheang150 Closed Dec 16, 2025
What version of Codex is running?
v0.73.0
What subscription do you have?
Azure enterprise
Which model were you using?
gpt4o_2024-05-13
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
Configured ~/.codex/config.toml as below
model = "gpt4o_2024-05-13"
model_provider = "azure"
[model_providers.azure]
name = "GenAi Gateway - gpt4o"
base_url = "https://nwgateway-appdev.kepler-prod.shared.banksvcs.net/genai/openai/gpt4o/openai/deployments/gpt4o_2024-05-13"
wire_api = "chat"
env_key = "OPENAI_API_KEY"
query_params = { api-version = "2024-10-21" }
PS C:\dev\workspace> codex hello
╭────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.73.0) │
│ │
│ model: gpt4o_2024-05-13 /model to change │
│ directory: C:\dev\workspace │
╰────────────────────────────────────────────────╯
Tip: Type / to open the command popup; Tab autocompletes slash commands and saved prompts.
› hello
⚠ Support for the "chat" wire API is deprecated and will soon be removed. Update your model provider definition in config.toml to use wire_api = "responses".
■ We're currently experiencing high demand, which may cause temporary errors.
The status started with Working, then Reconnecting and finally the high demand error. I've tried to eliminate the possibility of custom endpoint issue by running curl and both curl and codex is using the same JWT token.
PS C:\dev> curl.exe -X POST `
>> "https://nwgateway-appdev.kepler-prod.shared.banksvcs.net/genai/openai/gpt4o/openai/deployments/gpt4o_2024-05-13/chat/completions?api-version=2024-10-21" `
>> -H "Content-Type: application/json" `
>> -H "Authorization: Bearer $OPENAI_API_KEY" `
>> -d '{\"messages\": [{\"role\": \"user\", \"content\": \"hello\"}]}'
{"choices":[{"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}},"finish_reason":"stop","index":0,"logprobs":null,"message":{"annotations":[],"content":"Hi there! How can I assist you today?","refusal":null,"role":"assistant"}}],"created":1765898528,"id":"chatcmpl-CnRAGzUlEZYGikSBhgMAxz4Dp013M","model":"gpt-4o-2024-05-13","object":"chat.completion","prompt_filter_results":[{"prompt_index":0,"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}}}],"system_fingerprint":"fp_ee1d74bde0","usage":{"completion_tokens":11,"completion_tokens_details":{"accepted_prediction_tokens":0,"audio_tokens":0,"reasoning_tokens":0,"rejected_prediction_tokens":0},"prompt_tokens":8,"prompt_tokens_details":{"audio_tokens":0,"cached_tokens":0},"total_tokens":19}}
I have tried to restart codex session as well, the error seems to be consistent.
What steps can reproduce the bug?
Uploaded thread: 019b28e2-16a4-74c3-b947-785d1412039f
What is the expected behavior?
Codex should run fine
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗