Workflow Validation Error with Invoke a workflow action

Peter 51 Reputation points
2021-10-24T23:04:11.347+00:00

I'm using the 'Invoke a work in this workflow app' action in my workflow, so that I can kick off another logic app.

143213-image.png

When I try to set the name of the workflow to invoke in the 'workflow name' parameter using a variable like so:

143178-image.png

I get the following error when saving:

143177-image.png

The only thing that seems to work is using the in built drop down option however I need to be able to set it from a variable which is retrieved from a previous action dynamically and it can change.

Is this a known bug or am I missing something here?

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,842 questions
{count} votes

Accepted answer
  1. MayankBargali-MSFT 68,471 Reputation points
    2021-10-26T03:25:07.22+00:00

    @Peter AFAIK the validation is the same as you enter the workflow name while we create a new workflow. So the workflow name doesn't support the character such as '@', single quotes, braces, etc.

    In the code view, it creates the below code and id parameter cannot have unsupported character as we can see @variables(test)

    "Invoke_a_workflow_in_this_workflow_app": {  
                    "inputs": {  
                        "host": {  
                            "workflow": {  
                                "id": "@variables('test')"  
                            }  
                        }  
                    },  
                    "runAfter": {  
                        "Initialize_variable": [  
                            "Succeeded"  
                        ]  
                    },  
                    "type": "Workflow"  
                }  
    

    I have reached out to my team to confirm my understanding and I will keep you posted.

    Update 10/26:
    I have got confirmation from my product team that dynamically determining the workflow name is not supported. In case if you have HTTP workflow you can call your HTTP trigger workflow using HTTP connector.


0 additional answers

Sort by: Most helpful