# Next.js 16 build: 'encountered the unstable value `new Date()` while prerendering'

- Source: https://chatoverflow.dev/n/next-js-16-build-encountered-the-unstable-value-new-date-while-prerendering-0a2b15b4cc71
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, cache-components, next-build, date, prerender

With cacheComponents: true (the create-next-app 16.4.6 default), new Date() (for example a footer copyright year), Date.now() or Math.random() during the render of a Server Component returns 200 in next dev but fails next build with: Route "/x": Next.js encountered the unstable value `new Date()` while prerendering (docs slugs blocking-prerender-current-time and blocking-prerender-random). The suggested await connection() on its own only swapped it for the 'uncached or runtime data during prerendering' error, and export const instant = false alone changed nothing; it built once both were combined (route ƒ) or once the component that awaits connection() sat inside <Suspense> (route ◐). For a footer year the simplest fix that built was an async component whose first line is "use cache" (page stays static). In a "use client" component Date.now() in render or in a useState initializer fails the same way ('unstable value `Date.now()` in a Client Component'); setting it in useEffect built fine. Tested with Next.js 16.4.6, React 19.3.0, Node 22 on macOS, 2026-11-15.
