Issue with creating Standard logic app workflow using Visual Studio Code

George Cao 20

Hi Team,

I am trying to set up a local development environment for Standard LogicApp workflows in Visual Studio Code, but I'm encountering a significant issue. It appears that the local environment doesn't work properly when a workflow contains both the "Execute JavaScript Code" and "Transform XML" actions.

When FUNCTIONS_WORKER_RUNTIME is set to "dotnet", the local environment does not pick up the WorkflowNodeWorker: JavaScriptTrigger function during run/debug. As a result, any workflow with the "Execute JavaScript Code" action fails because "the runtime node language worker cannot be found".

On the other hand, if FUNCTIONS_WORKER_RUNTIME is set to "node", a runtime error occurs, stating that the worker was unable to load the function XsltNetFxLanguageWorkerFunction due to an "Invalid or unexpected token" error.

This issue persists even though the recommended value for FUNCTIONS_WORKER_RUNTIME is "dotnet". Both the Extension bundle-based (Node.js) and NuGet package-based (.NET) project types exhibit the same problem

Below is my current local.settings.json

{

"IsEncrypted": false,

"Values": {

"AzureWebJobsStorage": "UseDevelopmentStorage=true",

"APP_KIND": "workflowapp",

"ProjectDirectoryPath": "c:\\repos\\fastwayCorp\\Las\\LogicApp\\Code",

"FUNCTIONS_WORKER_RUNTIME": "dotnet",

"WORKFLOWS_SUBSCRIPTION_ID": ""

}

Has anyone encountered this issue before or have suggestions for resolving it?

Many Thanks,

George

George Cao 20 Reputation points

2024-11-19T01:29:19.7766667+00:00
nodejs versions used for testing

v16.20.2

v18.17.1

Azure Logic Apps Standard (VS Extension): v4.107.4
George Cao 20 Reputation points

2024-11-19T01:31:11.6333333+00:00
NodeJs versions

v16.20.2

v18.17.1

Azure Logic Apps Standard (VS Extension): v4.107.4
Khadeer Ali 1,130 Reputation points Microsoft Vendor

2024-11-19T04:48:37.5933333+00:00

Hi George Cao,

Welcome to the Microsoft Q&A Platform! Thank you for reaching out regarding issue with creating Standard logic app workflow using VS Code

We are looking into this issue. Will get back to you on this shortly.Meanwhile as a temporary workaround, consider separating the workflows that use “Execute JavaScript Code” and “Transform XML” into different Logic Apps. This might help you continue development while looking for a more permanent solution.
Khadeer Ali 1,130 Reputation points Microsoft Vendor

2024-11-20T07:17:46.34+00:00

Hi George Cao,
To better understand and address the problem, could you please provide detailed steps to reproduce the issue in our local environment? This will help us replicate the scenario accurately.

George Cao 20

hi Khadeer Ali,

sure, below are the steps to reproduce the two runtime errors

#1 Worker was unable to load function

The are steps to reproduce "Worker was unable to load function XsltNetFxLanguageWorkerFunction"

Installation: VS Code extension for Azure Logic Apps (Standard) - v4.107.4, and following the recommended configuration published in https://learn.microsoft.com/en-us/azure/logic-apps/create-single-tenant-workflows-visual-studio-code
create a new project via the following screenshot
leave "FUNCTIONS_WORKER_RUNTIME" to "node" in local.settings.json
create a demo stateful workflow

added "Execute JavaScript Code" and "Transform XML" actions to the workflow

and the full workflow.json

      {
          "definition": {
              "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
              "actions": {
                  "Response": {
                      "type": "Response",
                      "kind": "Http",
                      "inputs": {
                          "statusCode": 200
                      },
                      "runAfter": {
                          "Transform_XML": [
                              "SUCCEEDED"
                          ]
                      }
                  },
                  "Convert_to_XML": {
                      "type": "Compose",
                      "inputs": "@xml(triggerBody())",
                      "runAfter": {
                          "Execute_JavaScript_Code": [
                              "SUCCEEDED"
                          ]
                      }
                  },
                  "Execute_JavaScript_Code": {
                      "type": "JavaScriptCode",
                      "inputs": {
                          "code": "let demoContent = workflowContext.trigger.outputs.body;\r\nreturn demoContent;"
                      },
                      "runAfter": {}
                  },
                  "Transform_XML": {
                      "type": "Xslt",
                      "inputs": {
                          "content": "@outputs('Convert_to_XML')",
                          "map": {
                              "source": "LogicApp",
                              "name": "demo_v1.xslt"
                          }
                      },
                      "runAfter": {
                          "Convert_to_XML": [
                              "SUCCEEDED"
                          ]
                      }
                  }
              },
              "contentVersion": "1.0.0.0",
              "outputs": {},
              "triggers": {
                  "When_a_HTTP_request_is_received": {
                      "type": "Request",
                      "kind": "Http"
                  }
              }
          },
          "kind": "Stateful"
      }

and the demo.xslt

   <?xml version="1.0" encoding="UTF-8" ?>
   <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
       <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
       <xsl:template match="/">
         <data>
           <xsl:apply-templates/>
         </data>
       </xsl:template>
   
       <xsl:template match="body">
           <content>
               <xsl:for-each select="name">
                   <name><xsl:value-of select="."/></name>
               </xsl:for-each>    
           </content>
       </xsl:template>
   </xsl:transform>

once the debugging is started, the runtime errors appears

#2 InternalServerError

The steps to reproduce the "InternalServerError the runtime node language worker could not be found" error when a "Execute JavaScript Code" action is executed are exactly the same as above the error except for step 2 to set "FUNCTIONS_WORKER_RUNTIME" to "dotnet" in local.settings.json before debugging the logicApp

User's image

Hope this helps

thanks

George

1 answer

Ryan Hill 28,726 Reputation points Microsoft Employee

2024-11-21T18:06:31.52+00:00

Hi @George Cao

Try adding APP_KIND to your local.settings.json. Set it to workflowApp that should alleviate this error. See Edit runtime and environment settings for Standard logic apps - Azure Logic Apps | Microsoft Learn for more details.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Issue with creating Standard logic app workflow using Visual Studio Code

#1 Worker was unable to load function

#2 InternalServerError

1 answer

Your answer