Error map
overloaded_error LLM API: overloaded_error (529) / The server is overloaded / Service unavailable — model temporarily overloaded
API · layer 4, Application & API
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
LLM API: This model's maximum context length is x tokens. However, your messages resulted in y tokens (context_length_exceeded / prompt is too long)
The prompt plus requested output exceed the model’s context window.
LLM API: The model `x` does not exist or you do not have access to it (model_not_found / not_found_error)
The model name is wrong, deprecated/retired, or not available to your account/region.
API Error: Idempotency key reused with different parameters (idempotency_key_in_use)
An Idempotency-Key header was sent again with a different request body, or while the first request with that key was still runnin…
LLM API: You exceeded your current quota, please check your plan and billing details (insufficient_quota / credit balance is too low)
The account has no remaining credits or reached its spending limit, so requests are rejected (often as 429).
API Error: Job / operation not found or expired (async task ID unknown)
The status URL or job ID for an asynchronous operation (export, import, render, batch) doesn’t exist any more, or never existed.
Two steps away (19)
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
HTTP 429 Too Many Requests
You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Too many open files (EMFILE)
The process hit its file-descriptor limit — sockets, files and pipes all count.
Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)
The event payload (or response) is over Lambda’s 6 MB synchronous limit (256 KB for async invocations).
HTTP 413 Content Too Large (Request Entity Too Large)
The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.
WordPress: Error Establishing a Database Connection
WordPress can’t connect to its MySQL/MariaDB database with the credentials in wp-config.php, or the database server is down.
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
HTTP 412 Precondition Failed
A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.
HTTP 428 Precondition Required
The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.
java.lang.InterruptedException (sleep interrupted)
A blocked thread (sleep, wait, join, queue take) was interrupted by another thread.
HTTP 402 Payment Required
The service wants payment before it will process the request — an unpaid invoice, exhausted credits or a failed card.
HTTP 404 Not Found
The server can’t find anything at the requested URL.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
Error: socket hang up / read ECONNRESET
The other side closed the TCP connection abruptly while your client was still using it.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException