I get this warning on every safe in my development setup:
The ref ("...") was invalid. Now retrying with the latest master ref (...). If you were previewing content, the response will not include draft content.
I use Next.js 15 with the app router.
Has someone an idea what the problem can be?
1 Like
Ezekiel
(Ezekiel Ravidat)
January 31, 2025, 8:29am
2
Hi @andreas.markl ,
Can you give me a little bit more context on where and when this is happening?
Hey,
I can see this in my vercel logs. If I visit a special route and the request is not cached I get this warning like 50 times on the same request.
Ezekiel
(Ezekiel Ravidat)
February 3, 2025, 11:24am
4
Hi @andreas.markl ,
This looks similar to this issue:
Hello everyone!
I wanted to join the conversation as I built the Prismic website using Next.js.
I've encountered similar issues as all of you have reported after migrating to app router. I've tried various solutions over the past few months.
However, since version 14.0.2 , we haven't experienced any problems with revalidateTag() not revalidating.
The only unconventional setup we still have in place is VERCEL_FORCE_NO_BUILD_CACHE=1. As Nathan mentioned earlier, this is used to opt out of Verce…
Could you have a look and let me know if it helps?