Errors
AI API error troubleshooting
Use these notes to diagnose API proxy errors by code, likely cause, and the next check to run before switching providers or changing your setup.
Claude Code / Codex 503 No available accounts
Do not rotate keys first. This error usually points to an unavailable account pool, provider, group, or model route. Test a minimal request, confirm the model and group, then decide whether to wait, reduce context, change model, or switch provider.
Codex: Selected model is at capacity.
Error: Selected model is at capacity. Please try a different model. Treat it as model-level capacity, admission, or streaming interruption first. It can happen with ChatGPT-authenticated Codex CLI, proxy account pools, or Sub2API upstream overloaded passthrough.
Codex warning: Your conversation has multiple possible cybersecurity risk flags
Warning: Your conversation has multiple possible cybersecurity risk flags. Treat it as an OpenAI/Codex safety-routing signal first, then check whether an API proxy, sensitive keywords, long code context, or opaque model routing is making it worse.
Error 429 Too Many Requests for AI API proxies
Error: exceeded retry limit, last status: 429 Too Many Requests, request id: <request-id>. With an AI API proxy, repeated 429s usually mean the upstream account pool is rate limited, cooling down, or out of usable quota. Ask the provider to switch account, route, or model first.
Error 401 Unauthorized for AI API proxies
A 401 is an authentication failure. Check which key is loaded, which Base URL receives the request, whether the header format is correct, and whether the key is still active for that provider.