From eb9f0ad4800e74cd1ec0f9d72e4e180ace47db5d Mon Sep 17 00:00:00 2001 From: Ryan Albrecht Date: Thu, 19 Sep 2024 13:53:02 -0700 Subject: [PATCH] another spot --- docs/platforms/javascript/common/session-replay/issue-types.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/platforms/javascript/common/session-replay/issue-types.mdx b/docs/platforms/javascript/common/session-replay/issue-types.mdx index 28e336e122779..270bafb9bacee 100644 --- a/docs/platforms/javascript/common/session-replay/issue-types.mdx +++ b/docs/platforms/javascript/common/session-replay/issue-types.mdx @@ -39,8 +39,6 @@ Sometimes rage or dead clicks will be detected on elements which are not expecte ## Configuring Hydration Errors - - When a [hydration error](/product/issues/issue-details/replay-issues/hydration-error/) occurs in your React app, the SDK will emit an error object as well as a replay breadcrumb, both of which contain data about the hydration problem. Both of these are sent to the server for processing. When you're looking at the issue stream you'll see Hydration Error issues which could come from either data source. However, you will only see the diff tools which make debugging easier if a replay is associated with the error. For this reason we recommend having both [Inbound Filter](/concepts/data-management/filtering/) enabled and the "Create Hydration Error Issues" Replay setting enabled as well. This is also the default!