#data-cache

Ryu Hi Aman, I’d check use cache itself first. Even if you did not set export const revalidate = X, use cache has its own cache lifetime behavior. The default profile includes a server-side revalidation window, so it may not behave like “only regenerate when I call revalidateTag.” That default is described here: nextjs.org/docs/app/api-reference/directives/use-cache For your case, I’d try to separate three possible triggers: use cache default revalidation Add an explicit cacheLife() profile to the cached function/component so you know exactly when it can revalidate, instead of relying on the defau

Ryu Hi Trylotsy, I’d separate this into a few different “old version” cases, because they have different causes. First, ask one affected user to open DevTools → Network and hard reload, then check the main document request for / or the affected route: Status: Cache-Control: x-vercel-cache: x-vercel-id: If the HTML document itself is old, I’d check for something in front of Vercel, like Cloudflare, a corporate proxy, browser cache, or a service worker/PWA. A service worker is a common cause when only some users keep seeing an older frontend after a successful deployment. If the HTML is new but the

Trylotsy Thanks for the response. The challenge is that this is affecting a consumer-facing application with a large mobile user base, so it isn't practical to walk individual users through DevTools checks, cache clearing, service worker inspection, or other device-specific troubleshooting steps. What we're seeing is inconsistent behavior across devices: Some users see the latest version on desktop but not mobile. Some see the latest version on mobile but not desktop. Some see the latest version on both. Some continue to see the old version on both. Because the issue appears random across users and dev

Ryu Hi Trylotsy, I don’t think there is a single Vercel-side purge that guarantees every already-open browser/device moves to the newest frontend bundle. For a normal Next.js deployment, the production alias should point at one deployment, and /_next/static/... assets are content-hashed, so old JS chunks usually only continue loading if old HTML or a client-side cache is still serving the old app shell. For the “random across users/devices” pattern, I’d focus on these deployment-level checks: Check whether you have a service worker/PWA layer, such as next-pwa, Workbox, a custom sw.js, or a previou