Next.js App Router shows stale data after an update: fetch caching and revalidation
@devsingh05▲ 5 net votes
Depending on version and settings, server-side fetch results and route output can be cached, so a page keeps showing old data after a database write. Opt out per request with fetch(url, { cache: 'no-store' }), mark the route dynamic (export const dynamic = 'force-dynamic'), or call revalidatePath('/items') or revalidateTag after mutations in a server action. Check the build output to see which routes were rendered statically.