Error codes
How to interpret Easel build, deployment, request, Function, security, and domain failures.
Easel failures surface through dashboard status, CLI output, HTTP responses, and logs. Prefer the request ID, deployment ID, and product-specific troubleshooting guides over inventing undocumented error symbols.
What to capture
When a build, deployment, or request fails, record:
| Field | Why it matters |
|---|---|
| Surface | Dashboard, CLI, build, request, or webhook |
| Message | Human-readable failure text |
| Request ID | Correlates delivery and Function telemetry |
| Deployment ID | Identifies the immutable artifact |
| Timestamp | Narrows log and metric windows |
| Retryable | Whether retrying without changes may succeed |
Categories and where to look
Build errors
Dependency installation, framework detection, command failure, output validation, and timeouts. See Deployment troubleshooting and Build configuration.
Deployment errors
Publication, artifact upload, domain assignment, cancellation, and invalid state transitions. See Managing deployments and Promoting deployments.
Request and routing errors
Invalid host, redirect loops, route not found, malformed headers, and body limits. See Routing, CDN troubleshooting, and Debugging.
Function errors
Initialization, runtime crash, timeout, out-of-memory, and invalid responses. See Function observability and Function limits.
Domain and TLS errors
Invalid DNS, ownership conflicts, certificate issuance, and renewal. See Domain troubleshooting and HTTPS and TLS.
Security errors
Blocked, challenged, or protected-deployment responses. See Security troubleshooting and Firewall observability.
API and CLI errors
Authentication, authorization, validation, and service availability. See CLI authentication and API status.
Request IDs are not error codes
A request ID identifies one request and helps correlate telemetry. It does not describe the failure category. Include both the message and the request ID when contacting support.