Skip to content

Filter non-actionable "invalid origin" errors from Sentry#8414

Merged
iHiD merged 1 commit intomainfrom
fix/8394
Feb 8, 2026
Merged

Filter non-actionable "invalid origin" errors from Sentry#8414
iHiD merged 1 commit intomainfrom
fix/8394

Conversation

@iHiD
Copy link
Copy Markdown
Member

@iHiD iHiD commented Feb 8, 2026

Closes #8394

Summary

  • The "Error: invalid origin" is thrown by third-party iframe scripts (Cloudflare Turnstile, YouTube, Vimeo) during cross-origin postMessage communication — the string does not exist in our codebase
  • Added a filter in Sentry's beforeSend handler to drop these non-actionable errors, following the same pattern already used for dynamic import and Turnstile errors

Test plan

  • yarn test — 160 suites passed, 1550 tests passed
  • bundle exec rubocop --except Metrics — no offenses
  • bundle exec rails test:zeitwerk — Zeitwerk happy
  • After deploy: confirm "invalid origin" errors stop appearing in Sentry

🤖 Generated with Claude Code

@iHiD iHiD requested a review from dem4ron as a code owner February 8, 2026 20:01
The "Error: invalid origin" is thrown by third-party iframe scripts
(Cloudflare Turnstile, YouTube, Vimeo) during cross-origin postMessage
communication. These errors are not actionable and create noise in Sentry.

Closes #8394

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@iHiD iHiD merged commit 7f0bfb8 into main Feb 8, 2026
40 checks passed
@iHiD iHiD deleted the fix/8394 branch February 8, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error: invalid origin

1 participant