Hey @A_Learner
The “Should Stop” signal in UiPath allows for periodic checks during process execution to determine if the execution should be halted based on external conditions or triggers. It utilizes a dedicated activity called “Should Stop” within workflows, checking a stop signal flag that can be set externally. This mechanism is useful for handling long-running or iterative processes, enabling graceful termination and enhancing resilience and robustness in automation solutions.
In UiPath Orchestrator:
- Stop Job: This action allows you to gracefully terminate a running job. It allows the process to finish its current activity and perform any cleanup operations defined within the workflow before stopping. Stop Job is a controlled termination.
Scenario:
Suppose you have developed a process using RE Framework in Unattended Mode, and it is executing since 4 to 5hrs and you want to Stop the execution and need the output of recently executed transactions. In this scenario you will hit Stop button in Orchestrator!
- Kill Job: This action forcibly terminates a running job without allowing it to complete its current activity. Kill Job immediately terminates the process without performing any cleanup operations, potentially leaving resources in an inconsistent state. It’s an abrupt termination.
Scenario:
Same as Kill Job in Orchestrator!
In this Stop button will work as Kill execution, and it forcefully Stop the execution without generating final output!
If your query is resolved just mark the post as solution!
It will help others to find the correct solution.
Regards,
Ajay Mishra