Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,930 questions
##[warning]Error: Failed to update deployment history. Error: Conflict (CODE: 409)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 27%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Sergei Prokopov
11
Reputation points
When deploying application with Azure App Service deploy to staging slot, release shows that it succeeds, but there is
##[warning]Error: Failed to update deployment history. Error: Conflict (CODE: 409)
And auto swap with production slot does not happen, settings auto swap is set to true
Azure App Service
{count} vote
-
Udaiappa Ramachandran 726 Reputation points MVP2023-07-09T14:59:50.3766667+00:00 It is likely possible there may be some ongoing operations. Did you try the deployment again?
-
Sergei Prokopov 11 Reputation points
2023-07-09T16:08:34.2066667+00:00 All servers restarted, upgraded downgraded app plans, error is still there. No other deployments is going on.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 85%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Rishikesh Singh 470 Reputation points2023-07-09T16:53:41.0633333+00:00 what time of plan are you using have tried different web app plan, free plan have some limitations
-
Sergei Prokopov 11 Reputation points
2023-07-09T17:26:08.3366667+00:00 Hi, as mentioned: upgraded downgraded app plans. It was not a free plan initially.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
SnehaAgrawal-MSFT 22,706 Reputation points Moderator2023-07-13T06:25:41.7966667+00:00 @Sergei Prokopov Thanks for reaching here!
This conflict could be caused a CPU spike, an underlying storage capacity issue or something else. could you please check the app service storage quota to see if there's enough available space. If not, scaling your app service plan up would resolve the issue.
Also, see if there are any other deployments happening at the same time. If there are, wait for them to complete before attempting to deploy your application again.
Check if there are any issues with the deployment process. You can do this by reviewing the deployment logs and looking for any error messages or warnings.
You may try deploying your application again. If the issue persists, try deploying your application to a different staging slot or to the production slot.
see-https://learn.microsoft.com/en-us/azure/app-service/deploy-best-practices
Further- Before you configure auto swap for the production slot, consider testing auto swap on a nonproduction target slot.
for any problems, on swap see Troubleshoot swaps.
-
Sergei Prokopov 11 Reputation points
2023-07-13T06:37:27.4066667+00:00 Hi, as I have mentioned, I did upgrade. Additionally checked. File storage usage blow quota
No other deployments happening, it is the only one.The only error/warning I see is
##[warning]Error: Failed to update deployment history. Error: Conflict (CODE: 409)Can you improve logging and output conflicting resource or is there a way to see extra logs for that?
-
SnehaAgrawal-MSFT 22,706 Reputation points Moderator
2023-07-13T15:45:44.97+00:00 @Sergei Prokopov Could Please reach out to us by sending an email with subject line “Attn:Sneha |thread title” to AzCommunity[at]microsoft[dot]com referencing this thread would work closer on this issue.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 66%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
Christoph Bohner 0 Reputation points2023-07-17T07:50:08.89+00:00 Hi,
We have the same issue.
Did you find a way to fix this?We have the same setup for multiple applications and two of them started to fail swapping the slots.
No idea why...
-
Sergei Prokopov 11 Reputation points
2023-07-17T08:19:41.5733333+00:00 What I did is increased app service plan to next size, restarted all services, redeployed and changed back service plan. This helped to resolve slot swap, but the warning is still there.
Forwarded information to Microsoft.
-
Christoph Bohner 0 Reputation points
2023-07-21T11:04:28.3433333+00:00 Hi Sergei,
thanks a lot. Sadly, all tricks didn't work out, so we decided to turn off the auto-swap in the deployment slot but add a task in the azure DevOps deployment pipeline to trigger the switch. So we're getting notified, when the swapping is failed, as a bonus. -
Sergei Prokopov 11 Reputation points
2023-07-21T19:17:27.91+00:00 This release variable helped to see more detailed error message:
“system.debug” with the value “true”.
And from logs I see:
{"Message":"There is an auto swap deployment currently ongoing please try again when it completes."}}
Active DeploymentId :undefined
-
SnehaAgrawal-MSFT 22,706 Reputation points Moderator
2023-07-24T10:27:44.1966667+00:00 @Sergei Prokopov Thanks for sharing the information which helped you.
Sign in to comment
Sign in to answer