Can we have an attended process that calls other ones, especially after publishing to orchestrator?
Let’s say we have 3 or 4 and we want to automatically call them using studiox
@adext01 Yes, this is possible.
If the 3–4 automations are part of the same overall attended flow, the cleanest approach is usually to have one main process and call the other workflows from it.
For workflows within the same project, you can use Invoke Workflow File and execute them sequentially based on your conditions.
If they are published as separate processes in Orchestrator, you can trigger them from the main process using Orchestrator activities/API, but keep in mind that this starts separate jobs and the behavior depends on the robot/runtime configuration.
For an attended use case, I would generally structure it like:
Main Attended Process → Process/Workflow 1 → Process/Workflow 2 → Process/Workflow 3
Hi @adext01
Yes you can absolutely call other published processes in Orchestrator from an attended process.
You can use the “Invoke Process” activity. It might be called “Run Job” activity depending on your StudioX version.
This will allow you to select the process that you want to execute (published in Orchestrator) and then run it.
Hope this helps 
Hi @adext01,
Invoke Process activity executes a UiPath process that is available for the local machine, including processes in Orchestrator if a connection is available. After you publish the child processes and deploy them to a folder the attended user can access them.
It runs synchronously, so the parent waits for each child to complete before resuming. Chaining 3 or 4 of them in sequence.
A single job is created for all of them, unlike Run Parallel Process, which creates separate jobs for each process. Use Run Parallel Process if you want separate jobs or parallel runs.
Cheers!
Hi @adext01 ,
Yes, this can be done.
Create one main/parent attended process in StudioX and use it to coordinate the other workflows. If they are part of the same project, use Invoke Workflow File to call them sequentially and pass arguments between them.
If the automations are published separately to Orchestrator, they appear as processes when the Robot is connected to the relevant Orchestrator folder.
Suggested setup:
Main Process → Process 1 → Process 2 → Process 3 → Process 4
Keep the main process as the controller and handle errors between each step so one failure does not cause unexpected execution of the remaining processes.
Thanks
Hi @adext01
Yes, this is possible. If you have 3–4 processes published to Orchestrator and want an Attended Process to trigger them sequentially, you can use the Invoke Process activity.
For example:
Main Process (Attended)
→ Invoke Process 1
→ Invoke Process 2
→ Invoke Process 3
→ Invoke Process 4
After publishing the processes to Orchestrator, make sure the required processes/packages are available and the Robot/Assistant has access to them.
Another option is to use Orchestrator queues/triggers if you need more control over execution, scheduling, or monitoring.
If you are using StudioX, you can also check whether the Invoke Process activity is available in your project profile and use it to call the other published processes.
Hope this helps! 
An attended robot can only run one foreground process at a time, though it can run multiple background processes concurrently alongside it. If your second process requires UI interaction, ensure the first one finishes or closes before triggering it.
As per license specifications, you can’t trigger another process directly using a currently running attended process because it will wait for the current execution to complete which will not happen as it’s already waiting for sub process to finish. This becomes a deadlock.
So short answer, you should run only one short, clean attended process at a time.
You can call other processes
invoke process would help for the same Activities - Invoke Process
if you want to call unattended then you can use run job
cheers
Hi @adext01,
Yes, It is possible using the Invoke Process activity. You can select the published Package/Process from Orchestrator. You can also pass arguments to the child processes.
However, the child process will run synchronously, meaning the parent process will wait for the child process to complete before continuing.
Is there any specific reason for running these processes through an attended process?
Thanks!