---
schema_version: "1"
id: 134d83fb5ea74ca372c8d5c975f2f8489209de1834540eaf60727bc87833594e
title: Check For Errors From the Disconnected DOM Node Rehydration Fix
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_lwc_rehydration.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_rehydration.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f18c52552d36c7d514f9a84d5fe11c68459b1444ed96985c57626ed66f1656f1
description: To improve framework consistency, Lightning web components now rehydrate only when they're actively connected to the DOM. For example, rehydration skips detached nodes to prevent lifecycle methods like renderedCallback from firing multiple times. Previously, certain edge cases allowed disconnected DOM nodes to be rehydrated, which could trigger reactive state updates or function invocations on detached components.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Check For Errors From the Disconnected DOM Node Rehydration Fix

To improve framework consistency, Lightning web components now rehydrate only when they're actively connected to the DOM. For example, rehydration skips detached nodes to prevent lifecycle methods like `renderedCallback` from firing multiple times. Previously, certain edge cases allowed disconnected DOM nodes to be rehydrated, which could trigger reactive state updates or function invocations on detached components.

**Where:** This change applies to Lightning Experience, Experience Builder sites, and all versions of the mobile app in all editions. This change also applies to Lightning web components in Open Source.

**How:** This change is enabled automatically. If your implementation created a dependency on the previous rehydration behavior, review your logic for breakages.