From 16e3ab29d41898f7bc65db7601f381bee82f4159 Mon Sep 17 00:00:00 2001 From: Sonarly Claude Code Date: Thu, 2 Apr 2026 13:07:05 +0000 Subject: [PATCH] chore: improve monitoring for fix: gracefully handle transient 502 errors during MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Added `ignoreErrors` to the Sentry `init()` configuration in `SentryInitEffect.tsx` to filter out transient browser network errors that are not actionable: - `NetworkError when attempting to fetch resource` — Firefox's TypeError for failed fetch - `Failed to fetch` — Chrome/Edge's TypeError for failed fetch - `Load failed` — Safari's TypeError for failed fetch These errors occur when the browser loses connection to the server (e.g., during a transient 502 from Cloudflare). They are not bugs — they are symptoms of transient infrastructure availability that self-resolve. Capturing them in Sentry creates noise without actionable signal. --- .../modules/error-handler/components/SentryInitEffect.tsx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/packages/twenty-front/src/modules/error-handler/components/SentryInitEffect.tsx b/packages/twenty-front/src/modules/error-handler/components/SentryInitEffect.tsx index f90cabcecbc..e85665964fa 100644 --- a/packages/twenty-front/src/modules/error-handler/components/SentryInitEffect.tsx +++ b/packages/twenty-front/src/modules/error-handler/components/SentryInitEffect.tsx @@ -47,6 +47,12 @@ export const SentryInitEffect = () => { onunhandledrejection: false, // handled in PromiseRejectionEffect }), ], + ignoreErrors: [ + // Transient browser network errors from reverse proxy 502/503/504 + 'NetworkError when attempting to fetch resource', + 'Failed to fetch', + 'Load failed', + ], tracePropagationTargets: [ 'localhost:3001', REACT_APP_SERVER_BASE_URL,