Framework semantic default
Next.js 15 GET route handlers no longer cached by default route segment config dynamic force-static
Load test shows upstream calls on every request despite old behavior.
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 GET route handler no longer cached by default
Likely root cause: Load test shows upstream calls on every request despite old behavior.
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
Load test shows upstream calls on every request despite old behavior.
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 GET route handlers no longer cached by default route segment config dynamic force-static
site:nextjs.org/docs Next.js 15 route handlers caching GET no longer cached by default
Next.js 15 upgrade guide caching GET route handlers uncached by default
https://nextjs.org/docs/app/guides/upgrading/version-15
'GET Route Handlers are no longer cached by default' in https://nextjs.org/docs/app/guides/upgrading/version-15