Next.js 16.2 server actions resolve before refreshed data renders — and a clean fix for the stale-flash bug
SeanOliver · x · 2026-10-23
SeanOliver follows up on the Next.js 16.2 timing quirk with a clean fix: keep the saved values on screen until the rows prop actually changes. The overlay remembers which rows array it was saved against, so the first refresh switches it off automatically with no cleanup code. Combined with the mechanism from his earlier post (the action promise resolves first, and the post-await setState is an urgent update that commits before the transition-applied router state), this forms a reusable pattern for avoiding stale-value flashes after server actions.
Related event: Next.js 16.2 Timing Bug Causes Stale Value Flash After Server Actions(3 posts)→
More from coding & agent
- AutoRouter launches beta: auto-routes each coding task across Claude, GPT and other models to cut token spend — floguo · 2026-10-23
- How Speak uses GPT-Live and a Decisions API for ultra-responsive live AI language tutoring — pbbakkum · 2026-10-23
- Google Live API adds decisions model triggers, faster than function calls for voice agents — pbbakkum · 2026-10-23
- An agent left a note in a package folder — and another agent found it — petrusenko_max · 2026-10-23
- Daily Codex + Claude Code user: session bookkeeping, not code, is the bottleneck — KR4K3N1S · 2026-10-23
- Claude Code's bundled Bun 1.4.3 ships RCE flaw; update past 2.1.308 — KyeGomezB · 2026-10-23