Forum Discussion

TomasG's avatar
TomasG
Brass Contributor
Oct 22, 2024
Solved

How to solve issue: Incorrect worker runtime specified for function app (AZFD0013)?

Hi,  (I apologize if this post is placed incorrectly within the community.) we've used app Start/Stop VMs during off hours - V2 (https://github.com/microsoft/startstopv2-deployments) (https:/...
azure functions
  • TomasG's avatar
    TomasG
    Nov 08, 2024

    Hi Athithya 

    thank you for the response. Finally we received another email -
    Manually update Start/Stop VMs v2 Function App to .NET isolated model to ensure continued functionality

    based on that I did a manual update - which solved the problem.
    It is only necessary to wait about 1 day for the waring message to disappear.

    It can also be verified through the console when listing all files, where if the file StartStopAzureFunctions.dll has a date newer than Aug. 16, 2024, so the warning message should disappear automatically.

    More in the comments:
    https://github.com/microsoft/startstopv2-deployments/issues/143#issuecomment-2463440160

Athithya's avatar
Athithya
Brass Contributor
Nov 07, 2024

 

In future In-process model is going to deprecate anyhow. Better you can abide isolated model.

Yes. configuration setting is correct but please consider the below points

If you are using .NET framework application and/or .NET SDK like .net framework 4.8 or .net core 3.1, please convert your project to dot-net isolated model. You may need to change some nuget packages.

For example

In in-process model,

your function code starts as 

 [FunctionName("funcname")]

 

In isolated model, - after migrated from in-process

your function code will look like below and you need to make some changes in .csproj 

 [Function("funcname")]

 

Note:  FUNCTIONS_WORKER_RUNTIME value change can affect your func app code running

 

Please refer

https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net8

 

Resources