rob-thijssen

@shani11 @DawidNowak The combination of both `` and ` ` Was the fix for me in order to get functions v4 with net6.0 runtime working. Thank you both for the...

I am facing the same issue here. with LogicApp standard (west-europe). In the past I was able to edit the LogicApp workfl;ow that was originally deployed with Azure DevOps (zip...

@daverobinson64, I found out what was wrong with our LogicApps at our side. Due to a change in our deployment pipelines, the WEBSITE_RUN_FROM_PACKAGE was set to 1. This caused the...

Starting yesterday the error message automagically disappeared. Not showing anymore in the portal. I think the Azure team fixed something in the back-end?

I wonder if the following steps are the correct one to take to upgrade NuGet-based project for logicapps standard to v4? I followed the instructions mentioned on [this](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/azure-logic-apps-standard-now-supports-azure-functions-v4/ba-p/3656072) page. Now...

@rohithah, Thank you very much for you reply. I have only one question regarding your answer. I hope you can help me on this last one as well?? > You...

@oananicolaie, There's at least one thing I notice in your configuration: ``` FUNCTIONS_WORKER_RUNTIME: node WEBSITE_NODE_DEFAULT_VERSION: ~16 ``` `FUNCTIONS_WORKER_RUNTIME` should be set to `dotnet` `WEBSITE_NODE_DEFAULT_VERSION` can (should?) be removed