nextjs - 💡(How to fix) Fix Why is the router cache duration for statically rendered pages in Next 14 is 30 seconds, instead of the 5 minutes stated in the documentation? [2 comments, 3 participants]

TL;DR

The Router Cache Duration for statically rendered pages appears to be 30 seconds instead of the expected 5 minutes, causing the client to send requests to the server after the cache expires.

Guidance

• Verify the next.config.js file for any custom cache configurations that might be overriding the default Router Cache Duration.
• Check the Next.js documentation for any specific settings or environment variables that could be affecting the cache duration.
• Test the application with a different version of Next.js to see if the issue persists, potentially indicating a version-specific bug.
• Review the Vercel configuration, as the issue is observed on a Vercel-hosted demo, to ensure that there are no cache settings overriding the Next.js defaults.

Example

No specific code example is provided due to the lack of direct code references in the issue, but checking the next.config.js for something like experimental.cache settings could be a starting point.

Notes

The issue seems to be specific to the combination of Next.js version 14.2.35 and Vercel hosting. Without more details on the project's configuration, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by explicitly setting the cache duration in next.config.js if possible, as the current behavior does not match the documented expectations, and upgrading to a potentially fixed version is not explicitly suggested by the provided information.