Vercel: 504 FUNCTION_INVOCATION_TIMEOUT

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

// Raise the limit for one route (still capped by the plan)
export const maxDuration = 60;
export const runtime = 'nodejs';

// Streaming responses keep the connection alive and start sending early
export const runtime = 'edge';
return new Response(stream);

// Long jobs do not belong in a request: queue them
after(() => enqueue(job));    // next/server after()

// Serverless plus a normal Postgres pool exhausts connections and looks
// like a timeout: use a pooled connection string or a data proxy.

How to diagnose Serverless errors

Serverless errors are shaped by hard platform limits: execution duration, deployment package size, memory, and concurrency. Unlike a server you control, these cannot be tuned away. The fix is to restructure the workload. VPC-attached functions add a second class of problem, because they lose default internet access and depend on ENI capacity and NAT configuration.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

1. Check the platform limit before changing code: timeout, package size and memory are all documented, and the error is usually the limit being reported literally.
2. For timeouts, add timing logs around each external call. A function that times out is nearly always waiting on one downstream dependency.
3. Reduce package size with layers, tree-shaking, and by excluding dev dependencies and the provider SDK that the runtime already includes.
4. For VPC functions with no internet access, confirm there is a NAT Gateway or the relevant VPC endpoints. A function in a private subnet cannot reach the public internet by default.
5. Measure cold start separately from warm invocation in your metrics, and use provisioned concurrency only after confirming cold starts are the actual problem.

Tools worth reaching for

• CloudWatch Logs Insights
• aws lambda get-function-configuration
• X-Ray / distributed tracing
• sam local invoke

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

📖 vercel.com

Related Serverless errors

• AWS Lambda: ENI limit reached in VPCLambda functions in a VPC create ENIs (Elastic Network Interfaces) and the account or subnet…
• AWS Lambda: Internal server error, malformed Lambda proxy responseAPI Gateway received something it could not turn into an HTTP response. With proxy…
• AWS Lambda: Runtime exited with error: signal: killedThe function process was killed for exceeding its memory allocation. Lambda reports this…
• AWS Lambda: Runtime.ImportModuleErrorThe runtime could not load the handler module. Either the handler string does not match the…
• AWS Lambda: Task timed out after X secondsThe Lambda function did not complete within the configured timeout. Cold starts, slow…
• AWS Lambda: Unzipped size exceeds 250MB limitThe Lambda deployment package (unzipped) exceeds the 250MB limit. Too many dependencies or…
• Azure Functions: Host not runningThe Azure Functions host failed to start. Usually caused by invalid host.json, missing…
• Cloudflare Worker: Script size exceeds limitThe Cloudflare Worker script exceeds the 1MB (free) or 10MB (paid) compressed size limit.

See all 11 Serverless errors →

Browse other categories

• HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
• JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
• Database 41Connections, deadlocks, constraints, replication and memory limits.
• AI 35Rate limits, context windows, GPU memory and model-serving failures.
• Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
• Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
• Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
• Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
• System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
• Cloud 25IAM permissions, quotas, service limits and credential failures.
• Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
• TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.