The issue is simple: when I push to any branch, a Vercel deployment is triggered and immediately fails. This happens before the build is even run. The log is very short (I’ve redacted the github branch name + commit hash):
[16:33:20.710] Running build in Washington, D.C., USA (East) – iad1
[16:33:20.830] Cloning [REDACTED]
[16:33:40.538] Cloning [REDACTED]
[16:33:40.780] Error: This deployment is no longer building, it was probably canceled and/or deleted
[16:33:44.725]
This happens 100% of the time across all branches. Both Vercel and Github status pages are clear.
It could be related to project configuration. What happens if you try to deploy a new project? You can use a template like this one to check: Next.js Boilerplate
Thanks for the quick reply. I thought it might be configuration-related too, however if I simply redeploy a deployment that was already successfully deployed, I get the same error.
Thanks for giving it a try. I’m checking other similar build errors now since a few people have reported the same behavior. Will loop in the team to investigate
One would expect that to affect things after it has source. At the point of failure in the logs, it wouldn’t even have started npm: it’s still cloning the repo.
I’m having the same issue. I deployed earlier today around 11 am and had no issues. All of a sudden none of my deploys are working. I reverted all my changes thinking it was my code but the issue is not resolving. Is this just something we have to wait for npm to resolve? I’d appreciate any help thanks so much!
What happens if you try to deploy a new project? You can use a template like this one to check: 
