Back to list

Aggressive caching behavior causing stale data

6/10 Medium

Next.js 14 implemented aggressive default caching that led to stale data being served to users. While Next.js 15 disabled caching by default, this created a pendulum effect with new issues emerging in some cases.

Category
performance
Workaround
partial
Stage
debug
Freshness
worsening
Scope
framework
Upstream
wontfix
Recurring
Yes
Buyer Type
team
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Next.js in 2025?3/27/2026

Next.js 14's aggressive caching sometimes led to stale data. Although Next.js 15 disabled caching by default to address these complaints, new issues have emerged in some cases.

Created: 3/27/2026Updated: 3/27/2026