Worker saturation manifests as nginx 499 status codes

When Gunicorn workers are saturated with slow requests, clients timeout and close connections before receiving responses, appearing as 499 status codes in nginx logs.

Check nginx error logs for 499 status codes occurring at the time of worker terminations. Use faulthandler to capture stack traces to identify which backend operation (database query, API call) is causing the saturation.