I reduced noisy client-side Sentry capture for expected GraphQL validation failures and added a test to lock behavior.
Changes made:
1) Added `GRAPHQL_VALIDATION_FAILED` to the non-reportable GraphQL error codes in Apollo error handling.
- File: `packages/twenty-front/src/modules/apollo/services/apollo.factory.ts`
- In the error-code switch, `GRAPHQL_VALIDATION_FAILED` now returns early (same handling as other expected 4xx-style GraphQL errors), preventing unnecessary Sentry error events.
2) Added a unit test to verify these validation errors are not sent to Sentry.
- File: `packages/twenty-front/src/modules/apollo/services/__tests__/apollo.factory.test.ts`
- Mocked `@sentry/react` and asserted `captureException` is not called when error code is `GRAPHQL_VALIDATION_FAILED` (using the `licensedProducts` validation message example).
This keeps actionable monitoring signal cleaner by filtering expected schema/client-shape mismatches that are already handled.
Sonarly Claude Code
2a30cdbe8e