Errors Not Appearing in Browser After Exceeding Sentry Quota - Maximum call stack size exceeded #14053
Description
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 SDK are you using?
@sentry/nextjs
SDK Version
8.34.0
Framework Version
Next 14.2.9
Link to Sentry event
https://cliq-digital.sentry.io/projects/cliq-analytics/?project=4508137133178880
Reproduction Example/SDK Setup
// This file configures the initialization of Sentry on the client.
// The config you add here will be used whenever a users loads a page in their browser.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/
import * as Sentry from '@sentry/nextjs';
Sentry.init({
dsn: 'https://408766b047c311d6e13c6532b76da20a@o4505347937009664.ingest.us.sentry.io/4508137133178880',
// Add optional integrations for additional features
integrations: [
Sentry.replayIntegration(),
Sentry.browserTracingIntegration(),
Sentry.browserProfilingIntegration(),
],
environment: process.env.NODE_ENV,
// Enable Sentry only in production
enabled: process.env.NODE_ENV === 'production',
// Filter out errors that match a certain pattern
ignoreErrors: ['CanceledError: canceled', 'Network Error'],
// Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
tracesSampleRate: 1,
// Define how likely Replay events are sampled.
// This sets the sample rate to be 10%. You may want this to be 100% while
// in development and sample at a lower rate in production
replaysSessionSampleRate: 0.1,
// Define how likely Replay events are sampled when an error occurs.
replaysOnErrorSampleRate: 1.0,
// Setting this option to true will print useful information to the console while you're setting up Sentry.
debug: false,
});Steps to Reproduce
I am using Sentry.io in SaaS mode for error tracking in my web application. Recently, I exceeded my Sentry event quota, and since then, I’ve noticed that errors no longer appear in my browser’s console or as uncaught errors.
Expected Result
Even if the Sentry quota is exceeded, I expect browser errors to be still logged locally (in the console) and be thrown.
Actual Result
After exceeding the quota, no errors appear in the browser. It feels as if Sentry is blocking them from occurring or being logged. I’ve temporarily disabled Sentry in my code, and the errors seem to show up again, so it seems related to the Sentry SDK.
When I disable Sentry using dsn: null, the errors start reappearing in the browser.
I would appreciate any guidance on whether this is expected behavior or if it might be an issue with the SDK. If this is expected, are there any workarounds for ensuring errors continue to show up in the browser when the Sentry quota is exceeded?
Thanks in advance for your help!