GitDocs
Framework semantic default

Next.js 15 client router cache back forward navigation stale data docs

Back/forward navigation refetches or loses expected stale data.

Next.jsWeb frameworkFramework semantic defaultnext15

Agent Quick Fix

Repair against the current Next.js contract, then keep the change narrow and source-backed.

Product: Next.js
Current-contract area: Next.js 15 client navigation cache semantics change
Likely root cause: Back/forward navigation refetches or loses expected stale data.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.

Symptom

Back/forward navigation refetches or loses expected stale data.

Why This Happens

Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.

Common Wrong Fixes

  • Changing local code without checking the current external contract.
  • Retrying the same install, build, or API call with no version/source change.
  • Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

Next.js 15 client router cache back forward navigation stale data docs
site:nextjs.org/docs Next.js 15 Router Cache staleTimes
https://nextjs.org/blog/next-15
'Router Cache' in https://nextjs.org/docs/app/guides/caching

Source Trail