How I can ignore revalidate value only for new routes generated on-demand
#App Router ISR ignore revalidate
distant marlin
hallow girderBOT
Hi @distant marlin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the knowledge sources provided, it seems that there might be some issues with the revalidation process when using the App Router in Next.js. Some users have reported that the revalidate value is ignored until the first cache is invalidated. Once that happens, updates happen instantaneously. However, this behavior might not be consistent and could depend on various factors such as the deployment environment and the specific version of Next.js being used.
Here is an example of how you might set the revalidate value in a server component:
export const revalidate = 0;
In this example, setting revalidate to 0 should theoretically prevent the page from being cached, but some users have reported that the page is still cached on the first render.
Unfortunately, the knowledge sources do not provide a direct solution for ignoring the revalidate value only for new routes generated on-demand. It might be worth checking the official Next.js documentation or reaching out to the Next.js community for more specific guidance.
Sources:
- Github Issue (open): Revalidate value ignored on page.tsx until first revalidation > Original post Part 3 (https://github.com/vercel/next.js/issues/54460)
- Github Issue (closed): On-Demand Revalidation does not revalidate when using the App Router and deployed to Vercel > Original post Part 1 (https://github.com/vercel/next.js/issues/50714)
- Github Issue (open): App router : ISR always regenerates dynamic routes even when called with same params > Original post (https://github.com/vercel/next.js/issues/62195)