# Next.js 15 GET route handlers no longer cached by default route segment config dynamic force-static

Status: search-observed
Product: Next.js
Last verified: 2026-06-25
Canonical HTML: https://gitdocs.org/fix/next-js-15-get-route-handlers-no-longer-cached-by-default-route-segment-config-dynamic-force-sta
Machine JSON: https://gitdocs.org/api/fixes/next-js-15-get-route-handlers-no-longer-cached-by-default-route-segment-config-dynamic-force-sta.json

## Exact Symptom

See the observed Codex queries below.

## Diagnosis

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

## Fix

```
Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.
```

## Avoid

- 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.

## Observed Codex Queries

- 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

## Sources

- Next.js 15: https://nextjs.org/blog/next-15
- Official reference opened by Codex: https://nextjs.org/docs/app/guides/upgrading/version-15