Deployment fails with timeout

[vsesh]

Describe the bug

Hello. I can't deploy a new version of my service due to a timeout error.

After the first error, the production environment stayed in the "Uploading" state. And keep in the state for the last 10 hours.

What I can do?

[cidthecoatrack]

I am having the same issue. First deployment worked, second deployment hangs.

[val-jesperballe]

We have same issue. Do we have any news? Have we created azure support tickets or anything?

[PerKortbek]

We are having the same issue.

[mz8i]

Perhaps unrelated depending on your setup (I think it's mostly related to Next.js hybrid apps), but check if the reason might be the /.swa/health.html health check not working

[Touzi-Mortadha]

Sometimes, if you have configured a redirection in your middleware (for example Next.js Middleware) and it's not properly configured, you might encounter a timeout error. Try removing the middleware, and if the deployment succeeds, you should revisit and correct the middleware configuration.

[cidthecoatrack]

I'll chime in that at least for my case, after retrying 3 times with no other code changes, it eventually succeeded. I'm going to add retries to my pipeline for now, but because there were no code changes (and I am not using Next.js, just Angular), I assume the issue is not code-related, but something lower level that is seemingly random.