Cloudflare: Error 524: A timeout occurred

524 means Cloudflare connected to the origin, sent the request, and the origin did not send an HTTP response before the Proxy Read Timeout. Cloudflare's current documentation gives the default as 125 seconds; older documentation and some platforms still quote 100 seconds. Enterprise customers can raise it up to 6,000 seconds.

For automation, 524 is common when a request triggers a long-running job on the server: a big export, a report, a slow search, or a webhook handler that does all its work before responding. Platforms that sit behind Cloudflare inherit this limit; for example, n8n Cloud documents that webhooks that do not respond within 100 seconds fail with 524.

For the site owner, the fix is to make the response faster or to move long work out of the request.

# pattern that avoids 524: accept fast, process later
POST /exports        -> 202 Accepted, {"job": "abc123"}
GET  /exports/abc123 -> {"status": "running"}
GET  /exports/abc123 -> {"status": "done", "url": "..."}

Design APIs and webhooks to respond quickly and do heavy work asynchronously. Monitor P95 origin response times in Cloudflare analytics; when they approach the timeout, optimize before users see 524. Generic gateway timeouts are covered in HTTP 504.