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

**URL:** https://community.prismic.io/t/error-fetching-content-the-provided-ref-is-no-longer-accessible/14155
**Category:** Developing with Prismic
**Tags:** nextjs
**Created:** [September 22, 2023, 2:26pm UTC](https://community.prismic.io/t/error-fetching-content-the-provided-ref-is-no-longer-accessible/14155 "2023-09-22T14:26:23Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![samlittlefair](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/samlittlefair/32/696_2.png) [@samlittlefair](https://community.prismic.io/u/samlittlefair)
#### Post date: [October 6, 2023, 3:27pm UTC](https://community.prismic.io/t/error-fetching-content-the-provided-ref-is-no-longer-accessible/14155/9 "2023-10-06T15:27:49Z")

</div>

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

> [@Caching issue with Next.js App Router - Vercel Deployment](https://community.prismic.io/t/caching-issue-with-next-js-app-router-vercel-deployment/13834):
>
> 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…

---

_[View the full topic](https://community.prismic.io/t/error-fetching-content-the-provided-ref-is-no-longer-accessible/14155)._