Deal with error spikes caused by SWC email campaigns

[travisbloom-cb]

Every time SWC team sends emails out to advocates we see a spike in error rates on the site. See this mixpanel view. Looking in sentry to correlate the error pages to actual exceptions yields examples like this. The error message is not helpful, but if you scroll down to the breadcrumbs you see we log the message "antifingerprint not defined yet. will try and handle event after its ready".

Investigating this error leads to this insight. It appear whats happening is that a percentage of advocates are using outlook, and their outlook app is scanning SWC when the email arrives.

We need to:

• figure out how ignore these kinds of email bot scans in Sentry
• figure out how to ignore these kinds of events in mixpanel

OR

• figure out to get the error to not occur (which seems unlikely)

[ghost]

According to this message and the docs from sentry, we should be able to ignore those errors on Sentry by just adding the following regex: /Non-Error promise rejection captured with value: Object Not Found/ to ignoreErrors inside Sentry.init.

This regex will filter out any string that contains the substring Non-Error promise rejection captured with value: Object Not Found, that is the immutable substring of the error message.

[travisbloom-cb]

According to this message and the docs from sentry, we should be able to ignore those errors on Sentry by just adding the following regex: /Non-Error promise rejection captured with value: Object Not Found/ to ignoreErrors inside Sentry.init.

This regex will filter out any string that contains the substring Non-Error promise rejection captured with value: Object Not Found, that is the immutable substring of the error message.

Yup, we do this here, now just need to figure out how to ignore in mixpanel

[travisbloom-cb]

@paulovictor-cb reopening as it didn't prevent the errors from triggering as expected

[mhamendes]

@olavoparno