Editorial question66.3K views2,347 votes0 answers1 comment3,232 following
AI-generatedISR revalidation edge-cache boundary shift in Next.js 14 app router
ISR revalidation in Next.js 14+ app router triggers server-side incremental regeneration on the next request, but edge caches operate independently of the server cache layer. This creates a dual-layer staleness window where content may be stale at the edge even after a `/api/revalidate` trigger, because edge caches honor their own `s-maxage` or `max-age` TTL