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

Package + Version

@sentry/browser@5.13.0

Description

We are receiving a high volume of exceptions that follow the same signature. They occur across all pages, and in all sorts of places with seemingly no discernible pattern. It occurs across all browsers with frequency roughly the same as usage.

UnhandledRejection Non-Error promise rejection captured with value: Timeout

In all cases the Exception is missing. There is no stack trace or additional information.

I’m pretty certain this is originating from third-party code, but without more information to go on I’ve been unable to pin this down.

I’m opening this as a bug because it feels like Sentry should be reporting additional information to help pinpoint the source of the error.

There is an existing issue for this that has been closed without any resolution: https://github.com/getsentry/sentry-javascript/issues/2210

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 17
Comments: 16 (5 by maintainers)

Most upvoted comments

The issue lies exactly there: https://www.gstatic.com/recaptcha/releases/P6KLRNy7h3K160ZmYNUOAce7/recaptcha__en.js

c.reject("Timeout ("+y+")")

H((vn.delete(P),"Timeout")

tl;dr - they reject with a primitive value, but should with new Error("timeout").

In this case, your best solution until they fix it is to ignore this kind of errors.

Sentry.init({
  beforeSend(event, hint) {
    if (hint.originalException === "Timeout") return null;
    return event;
  }
});

+45

kamilogorek on Mar 25, 2020

@JustFly1984 Yep. That’s Google for for you. No sheets given.

+19

Undistraction on Mar 25, 2020

Does anybody know how this timeout affects end users?

+11

malykhinvi on May 27, 2020

It depends on how your codebase is tied to the ReCaptcha SDK, but I’d say that in general, in most cases yes, it shouldn’t affect the end outcome.

kamilogorek on Sep 15, 2020

Also the sentry seems to capture it once user clicks on recaptcha and doesnot perform any submit action that causes timeout (“Verification expired. Check the checkbox again.”) in captcha and sentry catches that timeout error. Not a serious issue in my Nextjs side but still needs some fixing in sentry side. My question to sentry devs: Can we ignore this specific message ("UnhandledRejection: Non-Error promise rejection captured with value: Timeout ") from specific files using sentry config ??

ChetSocio on Jan 11, 2024

I’ve failed an issue in google bug tracker, but they don’t give a sheet

JustFly1984 on Mar 25, 2020

We had multiple issues like this and pinned it down to google recaptcha code. It is very flaky, so we got rid of recaptcha and errors disappeared

JustFly1984 on Mar 25, 2020

@kamilogorek Ah. I hadn’t considered quota. Thanks for clarifying.

Undistraction on Mar 30, 2020

@Undistraction filtered events are dropped for the end user. Otherwise, they’d count toward quota.

kamilogorek on Mar 30, 2020

@JustFly1984 Thanks for the confirmation. Recaptcha is my prime suspect. Unfortunately we cannot remove it. Looks like it maybe doesn’t unmount properly. Still feels like we should be able to get more info from the exception though.

Undistraction on Mar 25, 2020