This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(51.2, 60%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am experiencing an intermittent issue with app service deployment slots and warm-ups.
Every day we create a new app service plan, app service, and a deployment slot in North Europe region. The slot is configured with the auto swap feature enabled. Although we have not changed our code, a couple of weeks ago we started experiencing an intermittent issue suggesting something may have changed within app service as it was working reliably beforehand.
We create the infrastructure and then deploy to the slot using zip deploy. Autoswap starts and we poll the status API. Occasionally like today we are given an app service plan where all app services will fail to slot swap because the swap warmup always fails no matter what we do. The slot is configured with app settings WEBSITE_SWAP_WARMUP_PING_PATH = "/api/healthcheck" and WEBSITE_SWAP_WARMUP_PING_STATUSES="200" and even though that API is returning a 200 code the warm up always fails for all app services on that plan.
The error is
"Failed swapping site. Error: Cannot swap slots for site XXX because the application initialization in 'XXX' slot either took too long or failed. Please check AppInit module configuration or try using swap with preview if application initialization time is very long. "
However, we are certain the warm up returned a 200 status and no sites on that plan will succeed for a slot swap if WEBSITE_SWAP_WARMUP_PING_PATH is configured. If you remove the WEBSITE_SWAP_WARMUP_PING_PATH setting then the slot swap will succeed, (but the app does not get warmed up!)
The only workaround is to destroy the app service plan and recreate everything, whereby usually the deploy and slot swap with warmup will start working again.
Is it possible there is a bug in app service?
Hi @Alastair I noticed you created a support ticket. I will monitor but I do want to inform you that you don't need to delete the app service plan when performing a slot swap. Doing so removes your web worker, the underlying hardware, of your app service. Deleting the resource will also make it more difficult to troubleshoot.
![](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(57.599999999999994, 37%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYJ%3C/text%3E%3C/svg%3E)
I'm attempting to setup a warmup and I'm running into the same error.
Based on our app insights logs, I believe it's failing because it's trying to hit "/", opposed to the actual value we've specified in the config.
Thanks @Ryan Hill - yes have filed support ticket. Reason for deleting of app service plan as it is an easy way for us to get a fresh new instance which does not have the bug that fails the slot swaps
![](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(140.8, 53%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
I'm still seeing the same issue described by OP.
Has the fix mentioned by @Alistair-6698 been rolled out to West Europe do you know?
We were instructed to check the platform version to verify. Go to the app service WebApp Kudu Console > Environment and check the value of variable WEBSITE_PLATFORM_VERSION. 92 or later is supposed to have the fix for the slot swap issue in it.
This has been acknowledged as a bug in App Service by MS support and "will be rolled out in next release cycle (tentatively)."
Latests from our MS support engineer three months later:
As per the latest update we have received Engineering team, they are diligently working on the fix. Once we have the update on the fix deployment or any further updates I will keep you posted.
Today's update from support:
As per the recent update from Engineering team the fix will deployed during next platform upgrade release and the current ETA for the platform upgrade is February, 2021(Tentatively).
MS confirmed the fix for this has been rolled out to our region (North Europe) and it seems to have fixed the 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(70.4, 89%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Hello @Alastair we have been experiencing the same problem in West Europe for the last 3 or 4 weeks.
Now, to have auto swap back again, we had to remove WEBSITE_SWAP_WARMUP_PING_PATH and WEBSITE_SWAP_WARMUP_PING_STATUSES but this is not ideal (we need to warm the app up before swapping).
Update: it is only WEBSITE_SWAP_WARMUP_PING_STATUSES that prevents swap (both auto or manual).
So, if in the configuration we set WEBSITE_SWAP_WARMUP_PING_PATH only everything works fine. If we set WEBSITE_SWAP_WARMUP_PING_STATUSES too we get the error subject of this thread.
![](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(192, 95%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
This is still an issue on version 101.0.7.520, is there any update? This has been ongoing for years at this point?