534 Project Error
Crashed serverless functions or malformed responses from Edgio project code produce the 534 Project Error status code.
Usage
Edgio ran application logic in serverless compute workers deployed at edge locations. These workers handled server-side rendering, API routing, and middleware execution. When a worker threw an unhandled exception, crashed, or returned a response not conforming to HTTP, Edgio caught the failure and returned a 534 to the client.
Common causes include:
- An unhandled exception in the serverless function code (null reference, missing dependency, syntax error).
- The function returns an incomplete or malformed HTTP response (missing status line, invalid headers).
- Memory exhaustion within the serverless worker during execution.
- A misconfigured route handler producing no response at all.
Example
A client requests a page handled by an Edgio serverless function. The function throws an unhandled exception, and Edgio returns a 534 error.
Request
GET /dashboard HTTP/1.1
Host: www.example.re
Accept: text/html
Response
HTTP/1.1 534 Project Error
Date: Mon, 02 Mar 2026 14:25:00 GMT
Content-Type: text/html
Server: ECAcc (dce/26A1)
<html>
<head><title>534 Project Error</title></head>
<body>
<h1>534 Project Error</h1>
<p>An error occurred in the serverless function</p>
</body>
</html>
How to fix
Check the Edgio deployment logs for the failing
route. The platform logs unhandled exceptions with
stack traces identifying the exact line and function
where the error occurred. Access logs through the
Edgio console or via the edgio logs CLI command.
Add error handling around all async operations in the serverless function. Wrap database calls, API requests, and file operations in try/catch blocks and return a meaningful error response instead of letting exceptions propagate to the platform.
Verify all dependencies are installed and bundled
correctly. Missing npm packages or incorrect import
paths cause runtime errors when the worker loads.
Run a local build with edgio build and test with
edgio run before deploying.
Monitor memory usage in the serverless function. Edgio imposes memory limits on workers. Large in-memory data structures, unbounded caches, or memory leaks trigger out-of-memory crashes. Profile memory consumption locally and optimize allocations.
Test route handlers to confirm each path returns a
valid HTTP response. A handler exiting without
calling res.send(), res.end(), or equivalent
produces a malformed response Edgio interprets
as an application error.