I've been experiencing a strange problem whilst upgrading an in-process 6 function app to isolated worker 8. I've followed the guidelines here: to update my app to 8 and isolated worker (including setting <OutputType>Exe</OutputType> , <AzureFunctionsVersion>v4</AzureFunctionsVersion>, and <TargetFramework>net8.0</TargetFramework> in the csproj.

I've also updated the function app settings in the Azure portal to 8 isolated worker (from 6 in-process) and FUNCTIONS_WORKER_RUNTIME to dotnet-isolated. After deploying the updated version, the app itself appears to function correctly but I am seeing this warning each time in the Azure portal:

I've double, triple and quadruple checked the app dependencies and the Azure portal settings - everything matches the suggested setting/configuration but I'm still getting this warning. I even checked the deployed package against a successfully upgraded function app and all of the relevant configs and manifests match.

I have no idea what else I can check, or how the functions runtime has detected the application payload to be dotnet. Every config / manifest inside the deployment package has dotnet-isolated at the relevant point.

In case anyone had a similar issue and can help it would be much appreciated!

Thanks in advance

Updated C# function app to dotnet 8 isolated worker model and get warnings in the portal

I've been experiencing a strange problem whilst upgrading an in-process 6 function app to isolated worker 8. I've followed the guidelines here: https://learn.microsoft/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net8 to update my app to 8 and isolated worker (including setting <OutputType>Exe</OutputType> , <AzureFunctionsVersion>v4</AzureFunctionsVersion>, and <TargetFramework>net8.0</TargetFramework> in the csproj.

I've also updated the function app settings in the Azure portal to 8 isolated worker (from 6 in-process) and FUNCTIONS_WORKER_RUNTIME to dotnet-isolated. After deploying the updated version, the app itself appears to function correctly but I am seeing this warning each time in the Azure portal:

I've double, triple and quadruple checked the app dependencies and the Azure portal settings - everything matches the suggested setting/configuration but I'm still getting this warning. I even checked the deployed package against a successfully upgraded function app and all of the relevant configs and manifests match.

I have no idea what else I can check, or how the functions runtime has detected the application payload to be dotnet. Every config / manifest inside the deployment package has dotnet-isolated at the relevant point.

In case anyone had a similar issue and can help it would be much appreciated!

Thanks in advance

Updated C# function app to dotnet 8 isolated worker model and get warnings in the portal

• c#
• azure-functions

Share Improve this question Follow asked Mar 12 at 13:12 Stuart BrownStuart Brown 2311 silver badge33 bronze badges 0

Add a comment  | 

2 Answers 2

Sorted by: Reset to default 1

When we did the switch, we had that warning, too.

It usually goes away on its own if you made sure everything is set as it should (as is documented).

For good measure you can manually force a restart / updates.

That's what happened with us. I was looking for the cause and when I called it a day and returned the next, the warning was gone.

I also remember to have read exactly that in a Microsoft resource somewhere, but I cannot seem to find it, right now. Will add it later if/when I do.

Sometimes I had experienced with stuck warning message like you have, but function itself functioning fine. You can clean up the stuck warning message by yourself next way:

Navigate to storage account associated with with your Function App, then in Tables you can clear the error. Error format: "AzureFunctionsDiagnosticEventsDATEHERE"

If you clear the table and the error persists, then you did not fix the underlying problem. You can confirm this by checking the table for new records.