error when debugging logic app in vs code - Failed to start a new language worker for runtime: dotnet-isolated.

Question

Hi,

i am building a logic app standard on vs code with function worker runtime set to dotnet-isolated, while debugging the app i get the following error.

Failed to start a new language worker for runtime: dotnet-isolated.

i do have all the necessary prerequisites installed to run the logic app.

Answer 1

@Sumit Gaur Thanks for reaching out.

The error message "Failed to start a new language worker for runtime: dotnet-isolated" indicates that the Azure Functions runtime was unable to start a new instance of the .NET Isolated Process language worker. This can be caused by a number of issues, including missing dependencies, configuration issues, or problems with the Azure Functions runtime itself.

Here are a few things you can try to resolve this issue:

• Check your dependencies: Make sure that all of the dependencies required by your Azure Function are installed and up-to-date. This includes the .NET Core runtime, the Azure Functions Core Tools, and any other packages or libraries that your function depends on. For example if you are using the package Microsoft.WindowsAzure.Storage.blobs instead of Azure.Storage.Blobs in your project depend upon the code then you could observe the issue.
• Check your configuration: Make sure that your Azure Function is configured correctly, including any environment variables, connection strings, or other settings that are required for your function to run.
• Restart the Azure Functions runtime: Sometimes, simply restarting the Azure Functions runtime can resolve issues with language workers. You can do this by stopping and restarting the Azure Functions host process, or by restarting the Azure Functions runtime in the Azure portal.
• Check for updates: Make sure that you are running the latest version of the Azure Functions runtime and the .NET Isolated Process language worker. You can check for updates using the Azure Functions Core Tools or by checking the Azure Functions documentation.

In case if you still observe the issue then please share the sample project so we can review it.