CD

Cloudflare Developers•13mo ago•

32 replies

Brett Willis

~5% of our workers requests never return from Cloudflare after the worker returns

We recently migrated our production API backend onto Workers compute and now ~5% of requests never get a response. E.g. in devtools the requests remain pending forever (i.e. several minutes until I get bored), with no headers or status code received. Experiencing the issue across all browsers and client apps.
When I encounter it on my machine I am able to identify these requests in workers observability logs, and they appear as successful response i.e.

outcome: "ok"

outcome: "ok"

and

$cloudflare.event.response.status: 200

$cloudflare.event.response.status: 200

but they remain hanging and never return from Cloudflare's edge.
How can the response remain hanging in Cloudflare after the worker returns?? What mechanisms could be at play here?

Can someone give me tips on how to debug this? Can I give some Ray IDs or worker/account IDs to the team to investigate?

This ~5% failure rate on our API is causing frustration for our users and customers, so any urgent tips/ideas/support would be greatly appreciated