[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # Deployments are auto-cancelled, 100% of the time 404 views · 21 likes · 17 posts Benjamin (@thegoldenmule) · 2025-01-08 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. Any ideas? Amy Egan (@amyegan) · 2025-01-08 It could be related to project configuration. :thinking: What happens if you try to deploy a new project? You can use a template like this one to check: https://vercel.com/templates/next.js/nextjs-boilerplate ageno (@founders-7528) · 2025-01-08 · ♥ 1 same situation with me.seems to be an error on their end. Benjamin (@thegoldenmule) · 2025-01-08 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. Amy Egan (@amyegan) · 2025-01-08 · ♥ 2 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 Benjamin (@thegoldenmule) · 2025-01-08 Really appreciate it. I'm sure you're aware, but the inability to do any builds/deployments is extremely urgent. Kirill Tregubov (@kirilltregubov) · 2025-01-08 I have the same issue and using the vercel CLI with `vercel --force` successfully deploys. Should be enough for the urgent deploys. Cheers! Amy Egan (@amyegan) · 2025-01-08 Looks like npm is reporting [intermittent degraded installs](https://status.npmjs.org/incidents/jlqm624klvs2) Benjamin (@thegoldenmule) · 2025-01-08 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. Benjamin (@thegoldenmule) · 2025-01-08 This does indeed work for me, thank you! @amyegan Good info to pass along to the team as it proves it is not a config issue (or npm for that matter). Amy Egan (@amyegan) · 2025-01-08 · ♥ 2 We're still investigating to determine the actual cause. The npm incident was just the first thing I found that might be related :smile: Thank you for sharing the CLI workaround @kirilltregubov! Anyone looking for more info on how to use that option can find it here: [Deploying from local build](https://vercel.com/docs/cli/deploying-from-cli#deploying-from-local-build-prebuilt) Tmowreen97 (@tmowreen97) · 2025-01-08 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!   Amy Egan (@amyegan) · 2025-01-09 · ♥ 2 We just pushed a fix. Can you redeploy and let me know if it works for you now? Benjamin (@thegoldenmule) · 2025-01-09 · ♥ 4 Hey it's working! Thanks. Kirill Tregubov (@kirilltregubov) · 2025-01-09 · ♥ 4 Fixed for me also! Thank you to you and the team for resolving it within a day! Tmowreen97 (@tmowreen97) · 2025-01-09 · ♥ 4 Working for me!! Thanks for such a quick response, nice to be a part of such a helpful community :slight_smile: Stan (@1223bb) · 2025-01-09 · ♥ 2 Working here, too! Thank you! That was incredibly fast!
