# Error when deploying to Vercel, API ref not found

**URL:** <https://community.prismic.io/t/error-when-deploying-to-vercel-api-ref-not-found/14777>\
**Category:** Developing with Prismic\
**Tags:** nextjs\
**Created:** [December 16, 2023, 6:04pm UTC](https://community.prismic.io/t/error-when-deploying-to-vercel-api-ref-not-found/14777 "2023-12-16T18:04:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [December 18, 2023, 10:34am UTC](https://community.prismic.io/t/error-when-deploying-to-vercel-api-ref-not-found/14777/2 "2023-12-18T10:34:12Z")

</div>

Hi Luiz,

It sounds like this issue. Can you check if the solution works for you:

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

---

_[View the full topic](https://community.prismic.io/t/error-when-deploying-to-vercel-api-ref-not-found/14777)._