Hi All,
In the orchestrator one has the opportunities of triggering a process either by time or queue trigger. I am currently using one workspace with a few foreground processes all triggered by time triggers scheduled after each other.
I was wondering what would happen if I would have another process triggered by receiving an Email.
Example: A process is scheduled to run between 8:00am and 9:00am. One document is processed after another. But at 8:30am a Email is received. Would this result in…
a) pausing the scheduled process and continue with the process that is triggered by the email. What happens afterwards? Will the bot swith back to processing the scheduled process or stop?
b) processing the scheduled process until 9:00am and add the process triggered by the email to the schedule. Therefore, leading to processing this process after 9:00am.
@FelixGe
In UiPath Orchestrator, when you have multiple processes scheduled with different triggers, the behavior will depend on the priority and configuration of the triggers. Let’s consider the two scenarios you mentioned:
a) Pausing the scheduled process and continue with the process triggered by the Email:
If the process triggered by the Email has a higher priority or is set to run immediately upon receiving the Email, it will interrupt the scheduled process. The Orchestrator will pause the current running process to handle the higher priority trigger (Email) and execute the corresponding process. After the Email-triggered process completes, the Orchestrator will resume the execution of the originally scheduled process.
b) Processing the scheduled process until 9:00 am and add the process triggered by the Email to the schedule:
If the Email-triggered process is set to run at a specific time and not immediately upon receiving the Email, it will not interrupt the current scheduled process. The Orchestrator will allow the ongoing scheduled process to complete its execution between 8:00 am and 9:00 am. After 9:00 am, the Orchestrator will then trigger the Email-triggered process as per its own schedule.
It’s essential to configure the triggers and priorities carefully to ensure that your processes run as expected. You can set different priorities for triggers and processes, and you can also configure the time intervals for each trigger. By setting the correct priorities and scheduling for each process, you can control the order of execution and avoid unexpected interruptions.
Additionally, you can use the Orchestrator Jobs and Queues to manage the execution of multiple processes more efficiently. If a process needs to wait for an Email trigger or another event to occur, you can design it to check for the trigger and take appropriate action accordingly.
Remember that the behavior described above is based on typical configuration and priority settings in UiPath Orchestrator. It’s essential to thoroughly test your automation in a controlled environment to understand the exact behavior in your specific setup. Always monitor the Jobs and triggers closely to ensure your automation is running as intended.
a) If the orchestrator is designed to handle concurrent triggers, it may pause the scheduled process at 8:30 am when the email trigger is received. It will then start processing the email-triggered process, allowing both processes to run simultaneously. After the email-triggered process is completed, it may switch back to the scheduled process and continue processing it from where it left off. This allows for parallel processing and better utilization of resources.
b) If the orchestrator is set to handle triggers sequentially, it will prioritize the already scheduled process that runs between 8:00 am and 9:00 am. When the email trigger is received at 8:30 am, it will not interrupt the ongoing scheduled process but instead add the email-triggered process to the queue of processes to be executed after the scheduled one. As a result, the email-triggered process will be processed after 9:00 am.
Which behavior is followed depends on the configuration and logic implemented in the orchestrator. Some orchestrators may support concurrent processing by default, while others may need specific settings or code to enable it. Similarly, some orchestrators may queue up processes based on trigger time, while others may have more complex priority rules.
It’s essential to review the documentation or consult with the developers/administrators of the orchestrator you are using to understand its specific behavior and configuration options regarding concurrent triggers and process handling.
You can create different triggers for each of your processes. Triggers allow you to start processes automatically based on various conditions such as time, queue items, or external events and with the individual triggers set up for each process, they can run simultaneously based on their respective schedules or triggering conditions.
Anil_G
Yoichi
Niranjan_k
rikulsilva
Gayathri_Ramanathan
aquesada
22222222asas
Steven_McKeering
Shiva_Nikhil
sasi_poosarla