why is my deployment slot just saying service unavailable?

Question

we have a setup where we deploy a staging slot whereafter swapping with production.
worked fine until 4 hours ago .. now we just get "The service is unavailable." and the deploy script says :
Error: Failed to fetch Kudu App Settings. Error: Site Unavailable from Mini-ARR (CODE: 503)

Answer 1

@Hauke Petersen We understand you are having issues with your deployments to your deployment slot.

This issue could be related to idle timeout. We see that in Azure WebApp environment the ide timeout is set to 20 minutes by default. Once that time is finished there will be no more incoming request to SCM site. If your deployment process (fetch, build, deploy) takes longer than that, it will be abruptly terminated.

We suggest you set your WebApp's appSettings WEBSITE_SCM_IDLE_TIMEOUT_IN_MINUTES = <value>. For instance, set to 30 if your deployment will last at most 30 mins.

1. Navigate to portal.azure.com
2. Go to your web app in the portal
3. Select the 'Configuration' blade
4. Enter WEBSITE_SCM_IDLE_TIMEOUT_IN_MINUTES = <value> in the Application settings section.

You can also try to enable WebApp's AlwaysOn feature. Our infrastructure will send requests periodically to your SCM site to keep it alive.

Please let us know if either of these two solutions resolve your issue. If not, reply back to here so we can assist you further.