Edge cache

Help
1

Hello Vercel Support Team,

I am experiencing a persistent caching issue with my project saisonnales-app-v2. The production URL (https://saisonnales-app-v2.vercel.app/) is consistently displaying outdated data (old residents), despite recent and validated deployments.

I have confirmed that the content is up-to-date when I directly access the URL of the latest deployment (e.g., https://saisonnales-app-v2-xxxx.vercel.app/). This indicates that the problem is not with the deployed code itself, but rather with how the cache is being managed or purged for the production alias.

I have already attempted the following troubleshooting steps without success:

  1. I checked and tried modifying the vercel.json file configuration to add cache headers (Cache-Control: no-cache, no-store, must-revalidate).
  2. I manually removed and re-added the saisonnales-app-v2.vercel.app alias to the production environment via the Vercel dashboard.
  3. I redeployed the latest successful deployment, unchecking the “Use existing Build Cache” option to force a complete rebuild and cache purge.

I confirm that I am not using any external CDN or proxy in front of Vercel. Therefore, the issue appears to be internal to Vercel’s caching mechanism.

Could you please investigate my project and help me resolve this persistent cache issue on the production alias?

Thank you for your assistance.

Sincerely,

3

Hi, @jthomasse-6900! Welcome to the Vercel Community :waving_hand:

We appreciate your patience :folded_hands:

Could try a hard refresh on the production URL using Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)? If that doesn’t help, clear your browser cache completely and see if the problem persists. It’s also worth testing the production URL in an incognito or private window to rule out any local caching issues.

If you’re serving dynamic data (like the residents you mentioned), you’ll want to double-check your cache invalidation strategy. For example, use Incremental Static Regeneration (ISR) with appropriate revalidation times, or for data that always needs to be fresh, set revalidate: 0 on your dynamic routes. For API routes, ensure you’re setting the proper cache headers so responses don’t get stuck.

Let us know how you get on!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.