Hey, everybody—is there a way to find each ‘invoke workflow file’ where the workflow that needs to be invoked doesn’t actually exist? In the screenshot, it’s obvious that the workflow is missing. However, is there a way to find these invokes if the process becomes very complex? I tried validate + analyze project, yet I didn’t receive these errors. Kind regards.
Is that workflow deleted accidently?
if you have backup in orchestrator or local folder you can able to retrieve .
otherwise, sorry its very hard to retrieve.
1 Like
Just hit run and it would throw error with fullpath which is mot available…that way you can find all the missing details
Till these are cleared process would not run
Cheers
1 Like
The First solution finding all invoke activity, you need to use the global Search
you can view the same using outline option on UiPath
You can go to this path of the last deployed system.
%ProgramData%\UiPath\Packages
OR
“%userprofile%.nuget\packages`
@Julian_Muhlbauer you will get the package project and then you can get all the files and change the location as per your path.
1 Like
Ok, so to summarize: There’s no way to find every ‘invoke’ where the path is incorrect just by clicking something. For example, the Workflow Analyzer can check code for specific issues. It seems I might have to create a custom rule in WFA. Anyway, thanks to all of you. All of your suggestions kind of make sense, yet they still seem like a workaround to my problem. 
1 Like