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(316.8, 22%, 40%)' 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)
I am trying to deploy an Azure Function in python to a Function App, but I keep getting this error message in logs. Service Health shows no issue, I've double checked all connection strings, and checked the available solutions which suggest removing WEBSITE_RUN_FROM_PACKAGE from settings. This same function app was previously working fine, started having this issue two days ago.
Logs for the error as as follows:
Syncing triggers...
9:42:56 AM extract-attachment1: Syncing triggers (Attempt 2/6)...
9:43:07 AM extract-attachment1: Syncing triggers (Attempt 3/6)...
9:43:29 AM extract-attachment1: Syncing triggers (Attempt 4/6)...
9:44:11 AM extract-attachment1: Syncing triggers (Attempt 5/6)...
9:45:32 AM extract-attachment1: Syncing triggers (Attempt 6/6)...
9:45:34 AM: Error: Encountered an error (ServiceUnavailable) from host runtime.
An Azure service that provides an event-driven serverless compute platform.
![](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(278.4, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDK%3C/text%3E%3C/svg%3E)
Hi, I have the same question and looking for a help. Any help is appreciated.
Thanks,
Dev
The issue is resolved. It was caused by a library in requirements file, which had an OS level dependency. In my case it was psycopg2. I had to define the binary file name for psycopg2 instead of it's version name in the requirements file, and the issue was resolved.
![](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(176, 77%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
Usually I have seen bug in azure function app and logic app. I have re-created function app and problem was resolved. Microsoft will never accept that there is an issue with their host
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
1 deleted commentComments have been turned off. Learn more
![](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(195.2, 88%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
In my case it was a bad secret config missing in key vault
Amazing the self diagnose really helped
Then at the bottom I saw:
[ResolveWorkitem] SecretNotFound error while retrieving Key Vault Secret Reference @Microsoft.KeyVault(VaultName=XXXX;SecretName=xxxxx-access-key). Exception: KeyVaultResolver.Common.ReferenceResolverException: Exception of type 'KeyVaultResolver.Common.ReferenceResolverException ...
![](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(246.4, 59%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJG%3C/text%3E%3C/svg%3E)
In my case, I had set a timeout in the host.json file that was too large compared with the consumption plan.
Reducing the timeout value to an acceptable value solved the problem