Description

Hi, I have a Next.js (v15.3.2) app deployed on Vercel. Every push to my single branch (main) results in a successful build, but the production URL stubbornly serves the previous version of my site. Even after using Redeploy → Clear Cache & Redeploy, manually purging the edge cache, and verifying my Cache-Control headers, the new code never appeared.

What “Fix” Worked

• Deleting the Project: Removing the project from Vercel’s dashboard and re‑linking my Git repo.
• Recreating & Redeploying: First deploy on the fresh project immediately reflected my latest commit.

I want to understand that -

1. Why does deleting the project purge all layers of cache (build, edge, data) and metadata (env vars, framework presets, domain aliases) when explicit cache‑clear commands did not?
2. Is there a non‑destructive way (CLI/API or configuration) to achieve the same “clean slate” effect without deleting the project?
3. Could this behavior indicate an underlying bug in Vercel’s cache‑invalidation logic or my project setup?