Cloudflare closes the connection after 100 seconds. Long WordPress jobs — imports, backups, WooCommerce reports — exceed that even though they eventually finish.
Cloudflare closes the connection after 100 seconds. Long WordPress jobs — imports, backups, WooCommerce reports — exceed that even though they eventually finish.
Move long jobs to WP-Cron or a queue and return immediately. For admin-side imports, run them over a Grey-clouded (DNS-only) subdomain so Cloudflare's timeout does not apply.
WordPress has its own failure mode, but Cloudflare Error 524 has a wider set of causes. The most common one overall is: A single request genuinely takes longer than 100 seconds.
Move the work to a background job and return immediately with a status the client can poll. Long synchronous requests are fragile regardless of the CDN.
An external probe reports actual response time, which tells you how close normal requests are running to the limit before they tip over.
Cloudflare closes the connection after 100 seconds. Long WordPress jobs — imports, backups, WooCommerce reports — exceed that even though they eventually finish.
Move long jobs to WP-Cron or a queue and return immediately. For admin-side imports, run them over a Grey-clouded (DNS-only) subdomain so Cloudflare's timeout does not apply.
Cloudflare connected to the origin successfully, but the origin took longer than 100 seconds to send a complete response. The request is too slow, not unreachable.