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(262.40000000000003, 91%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHT%3C/text%3E%3C/svg%3E)
Hello,
On Friday my function apps were working properly.
Since today, when I tried to deploy from VS Code, I got the "Service Unavailable" error (screenshot 1).
When I check the activity logs, I get errors such as "The connection has been closed by the client while the server is still processing its request for 'Microsoft.Web" (screenshot 2). Or "Encountered an error (ServiceUnavailable) from host runtime." (screenshot 3).
When I go to "Functions" to Monitor the functions, I get the warning "Azure Functions runtime is unreachable" (screenshot 4), and when I open a function to see the code, I get "Editing functions in the portal is not supported for Linux Consumption Function Apps.", which is unexpected as I did have the code displayed there last week.
I did not change anything since last week when it worked fine.
I tried upgrading my version of Core Tools before re-deploying but I keep getting the same error.
I also tried Refresh, Restart, Stop and Start the Azure function app but it did not solve anything.
Please let me know if you need more information to help me solve this problem.
Thank you in advance,
Thomas Duvivier
Update: Here is more info about the error that is in the Activity Log.
@(HERMES) Thomas Duvivier Looks like you have performed multiple operation start/stop function app and the function runtime was not started up correctly by the time you have performed the operation. It look like your function app is working correctly now with two function trigger.
Hi, how is the stop/start related to the problem as it did not work before I did those steps ?
@(HERMES) Thomas Duvivier Can you confirm the exact timeframe (in UTC) when you have observed the issue first time when you have done the remote build?
I can see the operation around 6/8 11:32 UTC. You can verify the same from activity logs
I see 11:52 when looking at the logs.
Hi, I still get this service unavailable error, the retry parameter makes it workaround sometimes (or waiting before trying again) but not always. Do you have an idea where this could come from ? I get this problem from multiple azure function resources.
503 service unavailable will be caused for the following reasons
The suggestion is to look into the "Diagnose and solve problems" blade in the Function app and select the "Function app down or reporting" detector. This detector will show all the diagnostic information about the function app and its infrastructure. This will give some insights about the function host related issues. Also, check the Web app restarted section to see if there were any platform related issues that could contribute to 503 error. Please note that if you are running on Linux platform, then you would get information about the container recycles in the Web app restarted detector.
If you have already verified it at your end then the suggestion would open a support ticket with us to review the logs that cause service unavailable. If you don't have the support plan then please refer to my private comment so we can assist you further.