Framework semantic default
Next.js route handlers caching GET cached by default dynamic by default docs
A route that was expected to stay cached now executes on every request.
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 16 implicit cache assumption produces live data
Likely root cause: A route that was expected to stay cached now executes on every request.
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
A route that was expected to stay cached now executes on every request.
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.
site:nextjs.org Next.js 16 route handlers caching default dynamic every request cache route expected cached executes on every request
Next.js route handlers caching GET cached by default dynamic by default docs
https://nextjs.org/docs/app/building-your-application/routing/route-handlers
'not cached by default' in https://nextjs.org/docs/app/building-your-application/routing/route-handlers