429 Error - Existing Issue: "ignoreSentryErrors" option not available for latest release (version 7.1.1)

[davidlee0602]

Problem Statement

Following a previous issue raised by other members: #4582

Summary:
429 errors (hard cap on rate limit in sentry config / settings) would prevent the AWS lambda function from running successfully, even though the error is a sentry internal error and not an error that generated from the logic of the AWS lambda function itself.

To prevent 429 errors from stopping lambda function execution, the following fix was applied to versions 6.18 and above;
#4620
however, it seems to have not been excluded in versions 7.0.0 and above (not included in latest Sentry release).

Can this ignoreSentryErrors option be included in the latest versions (7.x.x and above) of the repo?

Please kindly review and advise :)

Solution Brainstorm

Apply #4620 fix into latest / future releases :)

[lforst]

Hi @davidlee0602, thanks for writing in. We generally don't want the SDK to throw ever, so we fixed the underlying issue, namely errors bubbling up while sending error events to Sentry in #5090. This change made the ignoreSentryErrors options redundant so we removed it in v7.

Please see corresponding entries in our changelog and migration docs.

I will mark this issue as resolved, however, if issues because of non-2xx responses come up again in current or future versions, feel free to ping us here.