How to fix "Deployment endpoint responded with status code 409" error when no deployment is on going

Question

Hi,

I'm currently experiencing a problem with my services wherein the pipeline fails with an azure deployment error.

WARNING: Deployment endpoint responded with status code 409

ERROR: There may be an ongoing deployment or your app setting has WEBSITE_RUN_FROM_PACKAGE

I checked the deployment logs via azure management portal and I don't have any thing running. Additionally, I've encountered this issue with several services since yesterday (from different resource groups), so I don't believe it's a one off.

Other things I tried:

-I changed the setting WEBSITE_RUN_FROM_PACKAGE as a debugging step, but this did not help

-I am using az webapp deployment instead of az webapp deploy which is apparently deprecated. I suppose it'd be reasonable to guess that this is related, but I also wouldn't expect a bug in this (and I'd rather not guess at solutions given the vagueness. Deprecated isn't the same as broken)

Thank you for any suggestions or help!

Answer 1

Hi @Daniel Pomerantz
Thanks for the question and using MS Q&A platform.
The "Deployment endpoint responded with status code 409" error usually indicates a conflict with the deployment process. This happens when there is an ongoing deployment or when the WEBSITE_RUN_FROM_PACKAGE setting prevents certain deployment operations.

1.Even if nothing appears in the logs, check the Azure portal for any stuck deployments.Run this command to check logs and detect deployment conflicts:

az webapp log tail --name <your-app-name> --resource-group <your-resource-group>

2.Disable WEBSITE_RUN_FROM_PACKAGE (If enabled)

• Go to Azure Portal → Your App → Configuration → WEBSITE_RUN_FROM_PACKAGE.
• Or use the Azure CLI:

az webapp config appsettings delete --name <your-app-name> --resource-group <your-resource-group> --setting-names WEBSITE_RUN_FROM_PACKAGE

3.Instead of the deprecated az webapp deployment, use the recommended az webapp deploy

az webapp deploy --name <your-app-name> --resource-group <your-resource-group> --src-path <your-package.zip>

4. If the issue persists across multiple services and resource groups, check the Azure status page to see if there are any ongoing outages or issues that might be affecting deployments.

references:
https://learn.microsoft.com/en-us/troubleshoot/azure/devops/azure-web-app-services-related-issues#common-issues-and-solutions
https://learn.microsoft.com/en-us/troubleshoot/azure/devops/resource-not-exist-error-services-deployment#symptoms