Why Your Next.js Links Freeze on Stale Tabs (And How to Fix It)

The Silent Killer of Next.js User Experience Imagine this: A user opens your Next.js application, browses a few pages, and then leaves the tab open while they go to lunch. When they return and click a navigation link, nothing happens. The page isn't frozen—they can scroll, hover over elements, and interact with the UI—but clicking any <Link> component simply does not navigate to the target route. If you check the network tab, you might even see a successful 200 OK fetch request to the RSC (React Server Component) payload, but the client-side router refuses to transition. Refreshing the page magically fixes everything. This is the "stale tab navigation bug," and it's a notoriously difficult edge case to debug in production Next.js applications (particularly around versions 14 and 15). It rarely happens during active development because we constantly refresh our local environments. But in production, it silently degrades the user experience, leading to frustrated users and mysterious bug