Expired Ref with Next.js App Router

[dmakos (David)]

Hey,
I had this issue before, what version of Next.js are you on?

Possible solutions:

Next.js Vercel revalidation error

What Next.js version are you on? Apparently v14.2.7 had some fix to cache: Ensure fetch cache TTL is updated properly by ijjk · Pull Request #69164 · vercel/next.js · GitHub So perhaps you could start from here. I had the same issue couple of weeks ago, popped out of the blue for our big website. I added access token (Access Token - Documentation - Prismic) and upgraded Next to latest and so far it's not happening. And I really really hope it won't.

The provided ref is no longer accessible, it has expired

Hi, I have Prismic with Next.js 14.2.5 deployed on Vercel. Recently I started to have issues with cache (I suppose?) when accessing some of the pages, on Vercel the logs are showing: The provided ref is no longer accessible, it has expired. Master ref is: XXX this breaks my pages and is returning 404's. This 404 page is now becoming cached for some reason and keeps displaying instead! The only way to get the pages back is to purge cache on Vercel. Why is this happening out of the blue? Anyo…