Topic hub pagination
Continue browsing this topic cluster with SEO-safe static pagination.
Developer's production application using OpenAI API hits rate limit (HTTP 429), needs to understand how to handle retries, increase limits, or optimize token usage for paid plans Includes evidence for OpenAI API troubleshooting demand.
Rate limit exceeded (max is: X requests/min; Y tokens/min) Fix 401 authentication error when using Azure AD tokens with Azure OpenAI SDK after client upgrade Includes evidence for OpenAI API troubleshooting demand.
AzureOpenAI with AAD bearer token passed via api_key returns 401 Unauthorized after upgrading to 2.34.0+ Add stable error code mapping for background/async OpenAI API responses so callers can distinguish retryable vs non-retryable failures Includes evidence for OpenAI API troubleshooting demand.
Background responses failures lack a stable code/name that maps to an exception class — asynchronous mode has no deterministic error contract Fix indefinite hanging on long OpenAI API calls caused by NAT gateway idle timeout dropping TCP connections without keepalive Includes evidence for OpenAI API troubleshooting demand.
Non-streaming OpenAI API calls silently hang forever behind NAT — default httpx transport has no TCP keepalive Developer running OpenAI API calls behind NAT gateway experiences infinite hangs on non-streaming calls (Responses API / completions.create()). Server-side succeeds but client blocks forever. Needs connection timeout or keepalive fix. Includes evidence for OpenAI API troubleshooting demand.
Non-streaming OpenAI API calls hang indefinitely behind NAT gateway — server generates response but client never receives it Developer using OpenAI Python SDK streaming encounters JSONDecodeError when server sends SSE events containing only meta-fields (retry, id, event) without a data field. Needs robust parsing. Includes evidence for OpenAI API troubleshooting demand.
JSONDecodeError: Expecting value: line 1 column 1 (char 0) — in openai/_streaming.py line 259 json.loads(self.data) Fix OpenAI API 429 insufficient_quota when running AI coding tools (Codex, Cursor) that depend on API key authentication Includes evidence for OpenAI API troubleshooting demand.
insufficient_quota — You are out of money Get stable machine-readable error codes mapped to SDK exception classes for OpenAI Responses API background mode failures Includes evidence for OpenAI API troubleshooting demand.
SDK does not raise typed exception for background mode failed runs — returns 200 OK with free-form error.code string How to handle background mode Responses API errors deterministically in Python SDK; map opaque error codes to typed exceptions for retry logic Includes evidence for OpenAI API troubleshooting demand.
Background responses failures lack a stable code/name that maps to an exception class — status="failed" returns opaque error.code (e.g. "server_error") with no SDK exception mapping; HTTP poll returns 200 OK so no typed exception raised Distinguish programmatic handling between quota exceeded 429 vs standard rate limit 429; prevent infinite retry loops on permanent quota errors Includes evidence for OpenAI API troubleshooting demand.
Error code: 429 - insufficient_quota: You exceeded your current quota, please check your plan and billing details Fix OpenAI SDK silent hangs caused by missing TCP keepalive, affecting deployments behind AWS NAT Gateway, GCP Cloud NAT, and ISP routers Includes evidence for OpenAI API troubleshooting demand.
Non-streaming OpenAI API calls hang indefinitely behind NAT gateway — neither side knows connection is dead, no timeout exception raised, call blocks forever Developer uses local OpenAI-compatible servers (llama.cpp, LM Studio, vLLM) with api_key="" and gets credential validation error after upgrading openai-python SDK v2.34.0+; needs workaround or fix to reconnect Includes evidence for OpenAI API troubleshooting demand.
api_key cannot be empty. Please create one at https://platform.openai.com and try again. Restore ability to dynamically update rate limits for GPT image models via the organization rate limits API Includes evidence for OpenAI API troubleshooting demand.
rate_limit_does_not_exist_for_org_and_model: The rate limit for model gpt-image-1 is not set for your organization — POST to v1/organization/projects/proj_XXXX/rate_limits returns invalid_request_error Fix openai-node SDK proxy support — dispatcher option not passed through to undici HTTP client when using ProxyAgent Includes evidence for OpenAI API troubleshooting demand.
APIConnectionError: Connection error — fetchOptions.dispatcher (ProxyAgent from undici) silently ignored by openai-node SDK causing connection errors behind corporate proxies Fix OpenAI rate limit error when hitting TPM (tokens per minute) limits in an organization workspace; needs strategy to manage or increase rate limits Includes evidence for OpenAI API troubleshooting demand.
Rate limit reached for gpt-4.1 in organization <org_id> on tokens per min (TPM): Limit X, Used Y, Requested Z How to programmatically classify and retry failed OpenAI Responses API background runs based on error code Includes evidence for OpenAI API troubleshooting demand.
background response status=failed returns opaque error.code without SDK exception mapping; HTTP poll returns 200 OK so no typed exception raised Fix OpenAI client treating insufficient_quota as rate limit — stop unnecessary retries, surface correct billing/quota error to end users Includes evidence for OpenAI API troubleshooting demand.
insufficient_quota error returned by OpenAI API but client library retries as rate_limit (429), causing misleading user messages after extended backoff periods Understand why ChatGPT Plus quota does not apply to third-party API calls; determine if separate credits required or if quota routing between first-party and third-party OAuth contexts is a product bug Includes evidence for OpenAI API troubleshooting demand.
429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription Fix unreliable error classification in OpenAI Python SDK when using /v1/responses background mode; needs stable error.type field mapped to SDK exception classes for proper retry logic Includes evidence for OpenAI API troubleshooting demand.
HTTP 200 OK poll returns error.code='server_error' with status='failed', no typed exception raised — retry/backoff logic cannot distinguish server_error vs rate_limit_exceeded Resolve discrepancy in how rate limit errors are returned by different OpenAI APIs so developers can handle throttling uniformly Includes evidence for OpenAI API troubleshooting demand.
Inconsistent rate limit error responses between Responses API and Chat Completions API