Skip to main content
The Error Analytics dashboard gives you a centralized view of all request errors across your deployed applications. Use it to spot error spikes, identify which endpoints or status codes are causing the most failures, and drill into individual failed requests to see full logs and timing. You can access error analytics per-app (from any app’s Errors tab) or globally across all apps at Dashboard > Apps > Errors. Filter by endpoint, status code, and date range to narrow down the issue.

​
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 Status Codes and Runner Behavior to understand what each code means for your runners and retries.

​
Common Error Patterns

StatusWhat it usually means
500Unhandled exception in your endpoint code. Runner stays alive.
502Runner crashed or connection was lost during processing.
503Runner is in a bad state and was terminated. Request is retried.
504Request exceeded timeout. Often from cold starts or heavy workloads.
429Concurrency limit reached. Request is re-queued automatically.
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