Error codes reference
The JOEL-xxx error code index, with causes and resolutions.
Updated November 4, 2026
Deployment errors are reported as JOEL-xxx codes. The numbering follows HTTP conventions.
Client errors
| Code | Meaning |
|---|---|
JOEL-400 Bad Request | The request did not include a problem to solve. Restate it with the goal and the metric it should move, then retry. |
JOEL-401 Unauthorized | Feedback was requested after the decision was already made. Include Joel earlier in the process. |
JOEL-404 Context Not Found | A design was shared without the problem it is meant to solve. Attach the brief and retry. |
JOEL-408 Request Timeout | A meeting ran over. Queued responses are delayed by the same amount. |
JOEL-409 Conflict | Two stakeholders shared two different roadmaps. The request is paused until your organization agrees on one. This error cannot be resolved on Joel's side. |
JOEL-429 Too Many Requests | More requests arrived than one person can answer. Prioritize them and retry. |
Server errors
| Code | Meaning |
|---|---|
JOEL-503 Service Unavailable | The request arrived during the scheduled maintenance window (04:00 to 10:30 ET). It is retried automatically at wake. See the status page. |
JOEL-504 Gateway Timeout | An upstream dependency is unavailable. See Degraded performance before coffee. |
If you see an error that is not listed here, report it in the chat.
Was this article helpful?