Setting the file. One moment.
Subchapter 7.39
references/support-topics/next-fetch-revalidate-floor.mdMarkdown1 KBView on GitHub
Next.js fetch options can set the route’s effective cache floor. Low revalidate, revalidate: 0, or cache: 'no-store' can explain uncached traffic and excessive ISR work.
Inspect route-tree fetch calls. Compare route revalidation with per-fetch cache, next.revalidate, tags, dynamic APIs, and duplicated URLs with conflicting options.
Do not raise freshness windows for pricing, inventory, auth, draft, or user-specific data unless the source proves stale reads are acceptable.
Name the observed cache or ISR signal, the lowest cache setting that controls the route, and the exact fetch line to change.