My production deployment is stuck on a stale version of my application, rendering a core feature unusable. I have now followed every single documented procedure and community suggestion for cache invalidation, and all of them have failed. This is a severe platform malfunction.
The issue is that the Edge Cache is not serving the latest deployment, regardless of any action taken.
Here is a complete timeline of our failed attempts:
-
Code Fixes: We identified and fixed the application bug in our codebase days ago. The correct code is in our main branch.
-
Standard Redeploys: We have pushed dozens of new deployments, all of which build successfully but are not served by your CDN.
-
“Redeploy without Cache” Button: We have used this option numerous times to no effect.
-
Manual Cache Purge: We have used the “Purge” button in the Data Cache section of our dashboard. This did not purge the stale Edge Cache.
-
Forced UI Change (“Canary” Test): We pushed a commit (7ca94fdc) with a highly visible UI change. The change never appeared on the live site.
-
Aggressive Cache-Control Headers: We implemented a vercel.json file (commit 490c3dfe) with no-store directives for Cache-Control, CDN-Cache-Control, and Vercel-CDN-Cache-Control as per your documentation. The platform completely ignored these headers.
-
Forced Build Cache Invalidation: As a final step, we set the VERCEL_FORCE_NO_BUILD_CACHE=1 environment variable and redeployed. This also failed to resolve the issue.
Conclusion:
We have definitively proven that every single mechanism for cache invalidation on the platform—automatic, manual, configuration-based (vercel.json), and environment variable-based—has failed for our project.
I have exhausted all possible solutions. I need support.