The provided ref is no longer accessible, it has expired

[dmakos (David)]

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?
Anyone experienced this before and managed to fix this?
How can I avoid this happening?

[Phil (Phil Snow)]

Hey David,

You can check out this thread and the various solutions suggested.

Caching issue with Next.js App Router - Vercel Deployment

Dear Prismic team I set up a new Next.js App Router project using your setup command npx @slicemachine/init@latest and walking trough your step by step setup guide. In previous versions, I never had issues deploying the site to Vercel and setting up Prismic Webhooks to trigger redeploys. With this new project it seems like there are some caching issues with Vercel: If I push a new commit to Github or if I edit content on Prismic, it triggers a new deploy correctly. Unfortunately those deplo…

Thanks.

[dmakos (David)]

Hi Phil,

Thanks, I opted in to use access token and so far it seems to be okay. But I think we need more time.
I also updated Next.js to latest v14.2.11 - crossed fingers we won't see this issue again as it's literally breaking production when content gets updated.