Rank, 14 days: 9 on the Next.js sheet
3 people reported
All time, since Sep 27.
Revalidation takes effect late
“The revalidated page is still served from the cache until the gap between the two clocks has elapsed.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/4118/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Revalidated cache entries still served when wall and monotonic clocks drift. Tag expiry is stamped with Date.now() but checked against performance.now(), so revalidateTag, revalidatePath or updateTag take effect late.
Is this your bug?
File my report- Where
- incremental cache
- Versions
- 16.3.5 to 16.4.5
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Original reports3, newest first
- next start: revalidatePath/revalidateTag take effect late when the wall clock runs ahead of the monotonic clock (tag expiry stamped with Date.now(), checked against performance.now())On GitHub#101136
- next start: a page revalidated with revalidateTag is still served for a few ms, because tag expiry is stamped with Date.now() but checked against performance.now()On GitHub#99710
- Tag invalidation stops working after the machine sleeps: tagsManifest mixes Date.now() and performance.now()On GitHub#99329