RMD017 — A deferred hydration never resumed

A component returned a promise from @deferHydration, so the client adopted the server's markup and left the subtree untouched, waiting. The promise never settled.

The page therefore looks finished — the content is on screen, correct and complete — but nothing in that subtree responds. Usually a dynamic import that neither resolves nor rejects: a chunk removed by a deploy, a request that hangs.

Make the promise settle. A rejected promise still releases the subtree; only one that never settles leaves it frozen.

Next

• All diagnostics — every code the framework can report.
• Checking your app — the faults proved from the source, before anything runs.