Exception: UnhandledRejection: Non-Error promise rejection captured with value: Timeout

[ElenVlass]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/gatsby

SDK Version

6.15.0

Framework Version

Gatsby 2.32.3

Link to Sentry event

https://sentry.io/organizations/brocoders-z0/issues/2830974094/?project=5395466&query=is%3Aunresolved

Steps to Reproduce

In my app, I’ve received thousands (almost 5K for a month) of

UnhandledRejection: Non-Error promise rejection captured with value: Timeout

.
I’ve searched through our code and all compiled third-party code, looking for Timeout. This string isn’t thrown or passed to reject() anywhere. It’s pretty difficult to narrow down the root of the problem as there’s virtually no information about the script that is causing it. I suggest that this is coming from a third-part lib that loaded at runtime. Console points to this function in recaptch_en_gb.js:
"function" === typeof window[D] ? Promise.resolve().then(window[D]) : "function" === typeof D ? Promise.resolve().then(D) : D && console.log("reCAPTCHA couldn't find user-provided function: " + D)
It looks like the same issue as 2514 that has been closed.

Expected Result

I'm suggesting to add some custom code to @sentry/gatsby (if there isn't already) for handling this special case with non-Error types properly.

Actual Result

[lforst]

Hi, thanks for writing in! As a rule of thumb, we generally don't add code in the SDKs to handle specific errors of third parties. (There are some exceptions to this when we notice the impact is high enough - which in this case I don't believe it is)

What we recommend in this case is filtering your events via SDK configuration: https://docs.sentry.io/platforms/javascript/configuration/filtering/

Here, my specific recommend would be for you to use the ignoreErrors option or configuring the beforeSend option to drop these events, by looking at the error name and returning null if it matches the error you're describing.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀