Error map
RequestEntityTooLargeException Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)
AWS · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
Cloudflare Error 1025: Please check back later (Workers request limit)
The site’s Cloudflare Workers plan exceeded its daily request limit (free plan: 100,000 requests/day).
Cloudflare 413 Request Entity Too Large (upload over the plan limit)
The request body is larger than Cloudflare allows through the proxy — 100 MB on Free/Pro, 200 MB Business, 500 MB Enterprise defa…
API Gateway {"message": "Internal server error"} 502 — Malformed Lambda proxy response
The Lambda behind an API Gateway proxy integration returned something that isn’t the required {statusCode, headers, body} shape,…
Cloudflare Error 1102: Worker exceeded resource limits (CPU time / memory)
The Worker used more CPU time or memory than its plan allows for a single request.
InvalidParameterValueException: The role defined for the function cannot be assumed by Lambda
The execution role’s trust policy doesn’t allow lambda.amazonaws.com — or the role was just created and IAM hasn’t propagated yet.
fork: retry: Resource temporarily unavailable (process/thread limit)
The user or container hit its maximum number of processes/threads (ulimit -u, pids cgroup), so new processes can’t be created.
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.
Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'x'
Lambda couldn’t load your handler file or one of its dependencies — the package is missing from the deployment zip/layer or the h…
Runtime.HandlerNotFound: index.handler is undefined or not exported
Lambda loaded the file but couldn’t find the function named in the handler setting.
Lambda: Runtime exited with error: signal: killed (Runtime.ExitError)
The function process was killed — almost always because it ran out of its configured memory.
Lambda: Unzipped size must be smaller than 262144000 bytes
The function code plus layers exceed Lambda’s 250 MB unzipped limit for zip deployments.
Two steps away (33)
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
Too many open files (EMFILE)
The process hit its file-descriptor limit — sockets, files and pipes all count.
Cloudflare Error 1015: You are being rate limited
The site’s Cloudflare rate-limiting rule blocked you for sending too many requests in a short time.
Cloudflare Error 1019: Compute server error (Workers)
A Cloudflare Worker routed the request to a loop or hit an internal compute error.
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: The link you followed has expired
Usually an upload (theme, plugin, media) larger than PHP’s upload/post limits — WordPress receives an empty request and shows thi…
Upload error: File type not allowed / unsupported file type
The upload was rejected because the file’s type — extension, MIME type or actual content — isn’t on the allowed list.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
HTTP 502 Bad Gateway
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.
API Gateway: {"message": "Endpoint request timed out"} (504 after 29 seconds)
The backend (usually Lambda) didn’t respond within API Gateway’s integration timeout (29 seconds by default for REST APIs).
Cloudflare Error 1101: Worker threw exception
The Cloudflare Worker serving this route threw an uncaught JavaScript exception.
Cloudflare Error 1104: A variation of this script was not found (Worker route to deleted script)
A Worker route points to a script that no longer exists (deleted, renamed or not deployed to that environment).
wrangler / Cloudflare API: Authentication error [code: 10000]
The Cloudflare API rejected the token — it’s invalid, expired, missing permissions, or scoped to another account/zone.
WordPress: Sorry, you are not allowed to access this page.
Your user role lacks the capability for that admin screen — or the database table prefix / user capabilities are out of sync afte…
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::...:role/...
The caller can’t assume the role — either its own policy doesn’t allow sts:AssumeRole, or the role’s trust policy doesn’t trust t…
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
Error: write EPIPE
Node wrote to a pipe or socket whose other end was already closed.
RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded
child_process.exec/execSync produced more output than its buffer allows (default 1 MB).
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
GraphQL: Query is too complex / exceeds maximum operation depth / complexity limit
The server rejected the query because it’s too deep or too expensive according to its depth/complexity limits.
gRPC Error: 8 RESOURCE_EXHAUSTED: Received message larger than max (x vs. 4194304)
A gRPC message exceeded the receiver’s maximum size (4 MB default).
npm ERR! code ERESOLVE — unable to resolve dependency tree
npm 7+ found conflicting peer dependency requirements and refuses to install a broken tree.
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
Gradle: Could not resolve all files for configuration / Could not resolve dependency
Gradle couldn’t download a dependency — wrong coordinates/version, missing repository, offline mode, or network/proxy issues.
TypeError: x is not a function
You called something as a function, but its value is not a function (it’s undefined, a string, an object…).
OAuth Error: redirect_uri_mismatch
The redirect URI in your OAuth request doesn’t exactly match one registered for the client in the provider’s console.
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: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
java.lang.OutOfMemoryError: Java heap space
The JVM ran out of heap memory and garbage collection couldn’t free enough.
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException