Uncaught (in promise) resource closed - 608 times in 24 hours

Support
1

We’ve been getting this intermittent error shown to users (ecommerce website) for years now
we’re not sure what it is and what’s causing it because the error message doesn’t say much.
It looks as follows:
Jan 29, 05:40:12 PM: error Uncaught (in promise) resource closed
Jan 29, 05:42:12 PM: error Uncaught (in promise) resource closed
Jan 29, 06:02:45 PM: error Uncaught (in promise) resource closed
Jan 29, 06:03:46 PM: error Uncaught (in promise) resource closed
Jan 29, 06:08:21 PM: error Uncaught (in promise) resource closed
Jan 29, 06:19:08 PM: error Uncaught (in promise) resource closed
Jan 29, 06:23:22 PM: error Uncaught (in promise) resource closed
Jan 29, 06:23:37 PM: error Uncaught (in promise) resource closed
Jan 29, 06:27:45 PM: error Uncaught (in promise) resource closed
Jan 29, 06:31:00 PM: error Uncaught (in promise) resource closed
Jan 29, 06:39:52 PM: error Uncaught (in promise) resource closed
Jan 29, 06:39:56 PM: error Uncaught (in promise) resource closed
Jan 29, 06:56:53 PM: error Uncaught (in promise) resource closed
Jan 29, 06:57:04 PM: error Uncaught (in promise) resource closed
Jan 29, 06:57:09 PM: error Uncaught (in promise) resource closed
Jan 29, 07:03:52 PM: error Uncaught (in promise) resource closed
Jan 29, 07:17:14 PM: error Uncaught (in promise) resource closed
Jan 29, 07:27:49 PM: error Uncaught (in promise) resource closed

There are also other less frequent errors like “BadResource”:
Jan 29, 11:31:18 PM: 01KG61HM error BadResource: Cannot read body as underlying resource unavailable

I realise I may be reporting multiple issues here - the common theme is: I have not idea where the error is or what’s causing it.

One thing I noticed is that requests that may take longer than a few seconds may result in the most frequent error which is “error Uncaught (in promise) resource closed” but I might be wrong.

This is possibly contributing to serious losses to our store which we cannot quantify due to lack of proper reporting.

I cannot share a URL in public. If you need an app reference please get in touch privately. We’re paying customers.

A customer reported seeing this - we’ve also seen it when we reload a page with a backend component (loading data) multiple times:

crash
crash1164×2117 173 KB

Thanks

"This Edge Function has Crashed" - intermittent errors
3

Hey @indie :wave:,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!