Invoke Workflow Execution In RE framework Fails To Navigate To The File Path From The Actual Project Folder

News Knowledge Base
, , , , , , , , , ,
1

Why does Invoke workflow fail to navigate to the actual path? Invoke workflow doesn't work with relative path. The process fails when it's supposed to invoke a workflow, because it searches for it in the wrong location and can't find it. "Could not find part of the path"

This issue affected older Studio versions (like 2020.10, 21.10 and 22.4). A fix was released with version 22.10 of UiPath Studio.

In order to solve this, upgrade UiPath Studio to the latest version available.

If an upgrade is not feasible, the workaround is to add the absolute path in the Workflow File Name property of "Invoke Workflow file" activity.

Considering the below screenshot, enter the absolute path "C:\UiPath\nuget\Project A\1.0.1\lib\net45\Framework\TakeScreenshot.xaml" instead of the relative one "Framework\TakeScreenshot.xaml".