Error fetching content "The provided ref is no longer accessible"

[alain00.alvarez (Alain Alvarez Lopez)]

Hi, I'm having this error while fetching documents using a permanent access token, If I generate a new token the fetch works fine

response: {
    type: 'api_validation_error',
    message: 'The provided ref is no longer accessible, it has expired. Master ref is: ZQsdphAAACEA2FjG'
  }

[Pau]

Thanks for sharing your use case @alain00.alvarez.

Indeed, each time you get this type of error, you should use a valid and up-to-date ref when fetching documents using a permanent access token.

[jon1 (Jon Quayle)]

Hi,

I am having this exact issue, what exactly is causing this to occur? It actually took me a while to figure out what token was incorrect. Building my site locally works fine, but as soon as it is deployed to Vercel I get the error message?

Thanks

[samlittlefair]

Hey everyone,

We're looking into some issues around caching in Next.js. @alain00.alvarez and @jon1 are you both using the App Router?

Sam

[samlittlefair]

In the meantime, you can see if there's any helpful information here:

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…

[jon1 (Jon Quayle)]

Hi @samlittlefair, I am using the app router yes. Thanks for the link to this topic!

[ngiusti (Nick Giusti)]

Hey, I am also having this issue with Nuxt and Vue when deploying on netlify. Is there any update to this issue?

[nf_mastroianni (Neil)]

I feel like I was getting this issue among other strange cache issues. Adding the following to my package.json build script helped with Vercel build issues. Locally, I just nuked the .next folder entirely and ran a build and no issues:

"build": "rm -rf .next/cache/fetch-cache && next build"

Anyone else want to test this?

[samlittlefair]

@ngiusti If you're having this issue on Nuxt and Vue, it might be a separate error. Could you open a new thread and post your error message?

[samlittlefair]

Hey everyone,

We have opened a thread on the Next.js GitHub repository. Feel free to upvote and subscribe to follow along:

Inconsistent caching with `revalidateTag()` and Vercel Data Cache ·...

Sam

[jerry.nummi]

Is anyone else still experiencing this? I'm running Next 14.1.3

[nf_mastroianni (Neil)]

On occasion I see some “stranger things” related to refs. I just delete my .next folder locally and the issue goes away. Fortunately, I haven’t seen this issue in production in a while though.

[jerry.nummi]

Strange. I have it in Production but not locally.

[Phil (Phil Snow)]

Yes, this issue is mostly occurring in Vercel deployments. The following thread has some suggested fixes:

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…

[nicolecrst (Nicole Russo)]

Good afternoon, my Teach Lead and I managed to solve this problem in nextjs 14.2 using react's "cache" function. For now it is working well in our projects.

import { createClient } from '@prismicio/client'
import sm from '../../slicemachine.config.json'

export const client = createClient(
  `https://${sm.repositoryName}.cdn.prismic.io/api/v2`,
)

export const getTimeline = cache(async () => {
  return await client.getSingle('timeline')
})

[Phil (Phil Snow)]

Thank you for sharing your solution Nicole Although I'm curious as to what happens when you update the 'timeline' type? Can you test this and see if it works correctly?

And welcome to the community!

[nicolecrst (Nicole Russo)]

good morning! I went back to work on the project and got the "Unhandled Runtime Error Error: No documents were returned" error again, I deleted the .next cache folder and it corrected my error, I believe it is due to cache and conflict with other projects, informing which worked normally even without the react cache function after deleting the folder

[Phil (Phil Snow)]

I thought this might be an issue, and this is why we don't recommend using a cache with Prismic, especially for the main/master ref.