Don't capture errors for redirects

getsentry · Aug 30, 2023 · ea87659 · ea87659
1 parent 7e9415d
commit ea87659
Showing 1 changed file with 12 additions and 8 deletions.
diff --git a/packages/nextjs/src/common/wrapRouteHandlerWithSentry.ts b/packages/nextjs/src/common/wrapRouteHandlerWithSentry.ts
@@ -1,6 +1,7 @@
 import { addTracingExtensions, captureException, flush, getCurrentHub, runWithAsyncContext, trace } from '@sentry/core';
 import { addExceptionMechanism, tracingContextFromHeaders } from '@sentry/utils';
 
+import { isRedirectNavigationError } from './nextNavigationErrorUtils';
 import type { RouteHandlerContext } from './types';
 import { platformSupportsStreaming } from './utils/platformSupportsStreaming';
 
@@ -53,16 +54,19 @@ export function wrapRouteHandlerWithSentry<F extends (...args: any[]) => any>(
               return response;
             },
             error => {
-              captureException(error, scope => {
-                scope.addEventProcessor(event => {
-                  addExceptionMechanism(event, {
-                    handled: false,
+              // Next.js throws errors when calling `redirect()`. We don't wanna report these.
+              if (!isRedirectNavigationError(error)) {
+                captureException(error, scope => {
+                  scope.addEventProcessor(event => {
+                    addExceptionMechanism(event, {
+                      handled: false,
+                    });
+                    return event;
                   });
-                  return event;
-                });
 
-                return scope;
-              });
+                  return scope;
+                });
+              }
             },
           );
         } finally {