#edge-cache

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

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 Devansh, If those Sentry events cluster around deploy times, I’d treat this as version skew first. With dynamic(() => import(...), { ssr: false }), the browser may not request that CSS/JS chunk until later. If the user loaded HTML/JS from an older deployment, then a new production deployment goes live, that old client can later try to fetch a chunk URL that no longer exists on the deployment it is being routed to. That usually shows up as: Loading CSS chunk failed /_next/static/css/<hash>.css A good way to confirm is to check the failed asset request in Sentry or browser devtools: status: 4