My project's production domains have been serving a stale, outdated build for over 12 days, despite multiple fresh deployments and vercel promote confirming the latest deployment is current production.
Team/Project: vani-smartscheduler / subst
Affected domains: smartscheduler.in, www.smartscheduler.in, and even the plain default domain subst.vercel.app (no custom domain involved at all)
What I've already tried:
- Multiple fresh vercel --prod deployments
- vercel promote → confirms "already the current production deployment"
- vercel cache purge --type cdn --yes → run successfully several times
- Verified via headers that this is NOT a CDN cache issue — X-Vercel-Cache: MISS still returns the old content, meaning the origin itself is serving the wrong deployment
- Confirmed DNS resolves correctly to Vercel's infrastructure
Timeline: The issue started right after moving the domain smartscheduler.in from one project to another using the dashboard's "Add Existing" domain flow (Settings → Domains → Add Existing).
Latest (correct) deployment ID: dpl_4fTT8iNeTAXvUDn1Kmyz6cVHbmfA Bundle that should be served: assets/index-BvHuHheC.js Bundle actually being served: assets/index-D3Q1TA2o.js
This looks like a control-plane vs. serving-layer inconsistency on Vercel's infrastructure that's outside what I can fix via CLI or dashboard. Would appreciate help from the team — this has now been down for 12+ days.