Invoke Workflow Activity Problem

Help Studio
, , ,
1

I am using UiPath Studio version 2024.10.10 and client is using unattended bot.
Couple of days ago, when I ran a one process for the work. It worked fine. But, now the same process is giving me an error. It always happens at invoke work flow activity. Every parameters are set correctly. It gives me

“RemoteException wrapping System.Reflection.TargetInvocationException: Exception has been thrown by the target of invocation —> RemoteException wrapping System.IO.FileNotFoundException: Could not load file or assembly ‘ProcessName.MyProcess.processName, Version=5.0.18.0, Culture=neutral, PublicKeyToken=null’. Cannot find the file. …”

Do you know the issue? I tried erasing .local folder in the project folder. I tried making different workflow, but it is giving me similar error from the invoke workflow

Forum Engagement Daily Reports
2

Hi @kdlee

  • Republish the process
  • Clear UiPath cache and NuGet folders on the robot machine
  • Restart UiPath Robot service
  • Ensure all invoked workflows are from the same project/version
3

@kdlee

Make sure you are invoking the workflow which is part of your project and not outside of your project folder as the xamls outside of your project folder won’t be packaged into your budget package and will lead to this error.

4

It’s inside project folder’s folder. The problem is even invoking workflow for "Take Screenshot is giving me an error. Same error Could not load file or assembly. … at Source: System.Private.CoreLib At Source: System.Private.CoreLib. and it’s not working and giving me the same error

5

invoked workflows are inside the project’s folder, I did clear UiPath cache and Nuget folders. It’s still giving me same message.

6

@kdlee

Could you please share the packages you are using and their versions. Also the studio version.

It could be a bug. Try creating new sample process and test if the error persists. If yes, please share here so the product team can help on this.

7

the studio version 2024.10.10. I can’t share the packages in here. It’s a client’s company. but the invoke work flow for dependency package which is UiPath.System.Activities is 24.10.7

8

Rebuild and republish the process with a new version, delete .local / bin / obj folders, clear Robot .nuget and UiPath cache, restart Robot service, and ensure the job runs the latest package. Recreate Invoke Workflow if needed.

9

I did clear Robot .nuget and UiPath cache. and I did delete .local folder.

10
  1. Close Studio and delete the bin and obj folders inside the project.
  2. Open UiPath Studio as Administrator and rebuild the project.
  3. Increase the project version and publish again.
  4. In Orchestrator, delete older package versions and make sure only the latest one is used.
  5. Restart the UiPath Robot service or reboot the machine.
  6. Remove and re-add the Invoke Workflow activity, as references can break silently.
  7. Verify the project name and namespace haven’t changed and all invoked workflows are inside the same project.

In most cases this happens due to a corrupted package or Orchestrator still pointing to an old version.

11

It could be a bug. Try creating new sample process and test if the error persists. You can also delete invoke workfow activity and add it again and test it.

Usually re-deploying should solve this issue. Give it a try and let us know .

12

@kdlee
Did you update any packages recently?
Please check the version correctly and it should incorporate with studio version

13

@kdlee

did you embed one process in another process?

to verify just create a new process and invoke just one xaml and let us know if issues persists or its working

cheers

14

I didn’t update any packages, since the environment is in intranet.

15

yes some inside that invoke workflow activity there is another invoke workflow activity

17

@kdlee

invoke activity is fine..can you confirm with a dummy process once if invoke works

cheers

19

Doing the simple test as suggested by @Anil_G would be my first ask as well. @kdlee Could you please confirm if that dummy, “empty project” scenario works?

20

it works if I create a dummy invoke work flow activity with write line activity. But when I use the activities inside that previous one(it had for each folder activity), which was not working. It gives me an error. I don’t understand though. It was perfectly working that activity couple of days ago. and I didn’t really change anything from that on

21

@kdlee

This confirms there is no issue with invoke in the studio atleast

Can you show a screenshot of where and what is failing?

are you creating the workflow path dynamically?

cheers

22

invoke work flow works with some activities. But it is always giving me in certain invoke workflow activities. Right now at “Framework\InitAllApplications.xaml” invoke workflow which only has a log message inside, is giving me similar error “RemoteException wrapping System.IO.FileNotFoundException: Could not load file or assembly ‘ProcessName.Framework_InitAllApplications, Culture=neutral, PublicKeyToken=null’. File cannot be found. …”