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, 85%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWA%3C/text%3E%3C/svg%3E)
This request body works good in my local debug env, but in the cloud it returns 500, and this result doesn't inside the logs and app insight, everything looks good.
Besides, I added another function called "test" in there and publish to cloud but the function hub still got only one in there. And if I use postman to call the test function in the cloud will get the same result: 500.
You can navigate to application insights logs for your function app to verify what is causing the 500 error.
Looks like you have not specified the FUNCTIONS_WORKER_RUNTIME in your function app that is causing the issue.
Thanks for your notification.
You might noticed that the last log is in May 6th and there is no more log since that. And I viewed the Activity log and found there are log of "Update App Service Network Configuration failure " in May 8th, because we made some network changes during these days. And the storage service is inside the VN but the function is not, that is why it failed without any logs.
And I was wondering why there is no logs if the function failed because it lost connection with the storage. That should be very dangerous because if it could push some logs in app insight then we can using the alerts to send email or something to our staffs that fix it ASAP, but the function down for 3 weeks and nobody knows. If our customer doesn't contact us then it will continue off work.
@William A Wang Interesting, the logs should be pushed to the application insights whenever the function app gets called until there is an issue communicating with the function app and application insights (configuration issue). To troubleshoot it further I will suggest you to open a support ticket with us. If you don't have a support plan then please let me know.
What I told you is true, if the function and storage has disconnected then call func will fail and no more info gonna push into app insights.
You can try it your self, create a func a vnet and a storage, assign the storage inside vnet but func is not. Then you can test the func and see the result. I think you gonna have the same experience with me.
@William A Wang Can you confirm if post the changes are you getting 200 responses and getting logged? Can you share your application insights configuration? This could be an application insight configuration issue. AFAIK storage account will be used by the azure function when you are using timer trigger or you are communicating with the storage account.
The storage is inside a vnet, if I put the functions inside vnet it will get 200 and logged, if is outside vnet it will get 500 and no log.
The resource got only 2 functions, both are http triggered.
I wish to provide the app insight json to you but the comments seems have 1000 characters limitation.
@William A Wang My bad. Yes in scenario where function runtime is unreachable i.e. issue occurs when the Functions runtime can't start then there will be no logs written to the application insights. As your configuration would have AzureWebJobsStorage or WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and the function would not able to communicate with the storage account if you have not enable the exception "Allow trusted Microsoft services to access this storage account" at storage end.
<1/2>
Every function app requires a storage account to operate. If that account is deleted, your functions won't work.
Start by looking up your storage account name in your application settings. Either AzureWebJobsStorage or WEBSITE_CONTENTAZUREFILECONNECTIONSTRING contains the name of your storage account as part of a connection string. For more information, see App settings reference for Azure Functions.
<2/2>
But how to enable the "Allow trusted Microsoft services to access this storage account"
Correcting as Azure function are not yet supported as trusted services : https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal#grant-access-from-an-internet-ip-range
I viewed the storage networking settings the "Allow trusted Microsoft services to access this storage account" is already checked, but still can't access from functions which outside network.
I just think if the resource is failed no matter what cause the issue, the failed event should be logged. Do you agree with it?
@William A Wang In case of function runtime time host issue the runtime itself not working correctly so no logs will be logged. Only in case if the function runtime is working correctly but your function have some issue and resulting in 500 error then these logs will be logged.
But if the function runtime is not working correctly then the portal should give me some info about it, but currently I can't find any info about the function has disconnect with the storage, the status is still "running", everything looks good. If we didn't try to call the function we doesn't even know that there are some bad thing happened. If the feature doesn't log the error at least show me some warning in portal of functions should also be good. But there is nothing I can find that shows the functions are unhealthy.