# Caching issue with Next.js App Router - Vercel Deployment

**URL:** <https://community.prismic.io/t/caching-issue-with-next-js-app-router-vercel-deployment/13834>\
**Category:** Developing with Prismic\
**Created:** [August 8, 2023, 11:35am UTC](https://community.prismic.io/t/caching-issue-with-next-js-app-router-vercel-deployment/13834 "2023-08-08T11:35:57Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![ryan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/ryan/32/204_2.png) [@ryan](https://community.prismic.io/u/ryan)\
**Post date:** [October 10, 2023, 5:56pm UTC](https://community.prismic.io/t/caching-issue-with-next-js-app-router-vercel-deployment/13834/14 "2023-10-10T17:56:17Z")

</div>

> [@kyle](#):
>
> `rm -rf .next/cache/fetch-cache && next build`

This was helpful. We had a similar situation. When there is multiple [:uid]/page.js files, e.g. /[:uid]/page.js and /some-path/[:uid]/page.js

It seems like subsequent createClient() calls trigger a not-found repo error. There very well be some kind of fetch cache on createClient() or client.getAllByType(...).

After adding Kyle's suggestion:

- client.getByType('page')
- client.getAllByType('page')
- as well as creating a static array of uid's

All work as expected within generateStaticParams()

It probably stems from the changes in fetch with next.js 13.x and the app router. All fetch requests get cached by default (it think).

> **[Data Fetching: Incremental Static Regeneration (ISR) | Next.js](https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration)**
>
> Learn how to create or update static pages at runtime with Incremental Static Regeneration.

---

_[View the full topic](https://community.prismic.io/t/caching-issue-with-next-js-app-router-vercel-deployment/13834)._