Invoke workflow WorkflowFileName variable not supported

in legacy project, I could use a variable as workflow filename for invoke workflow activity. but after converting my legacy project to modern, it is no longer working.

is there any alternative to dynamically calling workflows? or workarounds?


Which version of UiPath.UiAutomation.Activities you are using, it is working fine for me with UiPath.UiAutomation.Activities version 21.10.5

Try to see if the Invoke Process activity helps.

I think you cannot do it dynamically in Windows and cross-platform projects. You need to specify manually.


No, dynamic invocation is not possible with compiled workflows.

Can you please detail what is your usecase? What are you trying to achieve and why is this needed?

our use case is:
there is a list of workflows that the user can choose to run. so the user can set up his list and then the automation will run the list for him. so if there are a lot of workflows to choose from, it is easier to automate with dynamic invocation rather than a long if-else or switch.

so anyway, i guess we will stay with legacy project for now

Hi there,

I have also encountered this issue migrating from Legacy over to modern Windows.

Our use case is an REFramework robot with a dynamic process layer, it is able to execute multiple different small steps/subroutines through a singular invoke activity. This works fine on legacy by setting the workflow file name/path as a variable from a config value and the input queue data.

By removing this function in modern windows, we now need to explicitly invoke 10+ hardcoded processes in a switch statement, which seems like a huge step back in terms of usability/functionality.

Are there any plans to re-integrate dynamic workflow, or a way to adjust the project.json to allow for dynamic workflow invocation within the modern windows ? @marian.platonov @alexandru



Just realised that I spend 15days trying to fix a bug with dynamically closing apps in the template just to find out that it’s not supported on Windows.

I’m gonna try dynamically generating the xaml file. Collecting workflows I want to call from one folder and generate a xaml file which will have invokes to each of them. That’s the only solution I have in mind rn.
This may cause problems when dynamically creating xaml files using packages in the Orchestrator. So there might be a need to create and call the file from some remote/non-orchestrator location.

Hi all, any update on this or any workaround?
I have been using dynamic paths for invoke workflow file activity, cause there’re a few hundred workflows with the same name format. It would be a painful process to use switch activity.

Hi, any update regarding this question?
I can’t see a viable solution without using variable paths with an operation for hundreds of robots.

Hello @alexandru
I have also few uses cases where the code need to be dynamic, based on conditions run different flows instead of having to create a huge Select Case, there is also a partner that is using the same approach to dynamically run code based on a list of steps provided


Any updates ? I have the same thing on our framework and i cannot continue migration.

I see that windows-legacy will be deprecated for creating projet : Studio - Deprecation of the Windows-Legacy Compatibility (

So UiPath teams what solution do we have ?

We have several use cases where workflow name was dynamically computed. How can you deprecate a framework if the new one does not offer old functionality? Please fix this issue @uipath

Any progress in mitigating this feature gap?


This was mentioned in release notes for CE 2023.10. So I’d expect it to be included in the enterprise release as well.

1 Like

Hello, I have a case which is similar to this one.
For me it helped to use the function “Invoke Process” instead of “Invoke Workflow File”.

You just have to publish the “subproject” to the orchestrator, but then you can use it similiar to the old activity, I think.