Framework semantic default
Next.js 15 fetch requests no longer cached by default force-cache revalidate official
Server component repeatedly hits a third-party API and rate limits.
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 fetch no longer cached by default
Likely root cause: Server component repeatedly hits a third-party API and rate limits.
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
Server component repeatedly hits a third-party API and rate limits.
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 fetch requests no longer cached by default force-cache revalidate official
site:nextjs.org/docs Next.js 15 fetch requests are no longer cached by default
https://nextjs.org/docs/app/guides/upgrading/version-15