Skip to main content

Why aren't my inbound filters filtering out all hydration errors?

Issue

I want to know why some hydration errors still appear in my project after I enable the React hydration errors inbound filter.

Applies To

  • All SaaS Customers

  • Error Monitoring

  • Inbound Filters

Resolution

The React hydration inbound filter only drops a fixed set of common React hydration messages, such as minified invariant URLs 418, 419, 421, 422, 423, and 425. Other hydration-related errors are still accepted.

  1. For those remaining error events, drop them in the SDK with ignoreErrors or beforeSend, using the minified message rather than the readable UI text. See Why aren't some hydration errors being dropped by the SDK?.

  2. If you still see Hydration Error issues with Session Replay on, they may be Replay Issues created by Create Hydration Error Issues. Inbound filters do not stop those. See Why am I still seeing Hydration Error issues?.

Overview of the filter type: Inbound Filters.

Did this answer your question?