Setting the file. One moment.
Subchapter 7.22
references/support-topics/cache-components-static-shell-boundaries.mdMarkdown1 KBView on GitHub
On Next.js 16 with Cache Components, avoid older segment-config advice. The right question is whether the route can keep a static shell while dynamic data moves behind explicit cached or runtime boundaries.
Check cacheComponents, use cache, cacheLife, request-time APIs, Suspense boundaries, and scanner evidence such as force-dynamic or headers-in-page.
Do not suggest dynamic, revalidate, or fetchCache as the primary fix when Cache Components is enabled. Do not cache request-personalized content.
Name the Next.js version, Cache Components state, dynamic trigger, and the exact boundary or directive that can change.