Debugging Errors
When you see errors in the dashboard, click into any individual failed request to see the full details: when it was submitted, how long it took, what status code was returned, and the complete request logs. This is the fastest way to go from “something is failing” to “here’s the stack trace.” For errors that correlate with a deployment, check App Events to see if a recent deploy or config change caused the issue. If the error rate is tied to a specific status code, see Retries and Error Handling to understand what each code means for your runners and retries.Common Error Patterns
For a complete reference on how each status code affects runners, retries, and billing, see Status Codes.
Status Codes
How each HTTP status code affects runners and retries
Retries
How fal automatically retries failed requests