Does a deploy that timed-out on the command-line keep running in the backend?

I haven’t deployed my site for 2.5 months, but it used to complete successfully in a matter of minutes.

Today, my command line deploy is timing out while waiting to go live:

✔ Finished hashing 15901 files
✔ CDN requesting 32 files
✔ Finished uploading 32 assets
⢹ Waiting for deploy to go live... ›   Warning:
 ›   {
 ›     "name": "TimeoutError"
 ›   }
⢺ Waiting for deploy to go live...    TimeoutError: Promise timed out after 1200000 milliseconds

But it still shows as “Deploy in progress” in the web control panel. The latest message in the web control pane is

3:37:17 PM: Creating deploy upload records

It’s still like this 35 minutes later. It’s a static site, but quite large (2GB) although I’m just deploying some very small changes today.

Should I keep waiting or assume it’s dead?

If it’s dead is there any way to diagnose what’s causing this timeout?

I’m using netlify-cli/2.54.0 darwin-x64 node-v12.18.1

1 Like

I’ve had the same issue, my build has been running for over 2 hours. The output in the deploys page is the same as yours:

4:28:53 PM: Creating deploy upload records

Netlify status page says everything is green.

Anyone from Netlify who knows what’s up? Is it a widespread issue?

netlify-cli/2.47.0 darwin-x64 node-v14.7.0

I updated my netlify-cli version with npm install -g netlify-cli and now new deploys are succeeding quickly. The old deploys are still stuck so I’ve cancelled them.

I can’t be sure if it’s the new version that caused this to start working again though.

1 Like

I can confirm that updating the CLI solved the issue for me too :+1: