REframework should stop

Help Studio
, ,
1

How does a bot receive a stop activity from Orchestrator?
Is it different than sopping the bot run from Studio?

Thank you.

2

Hi!

The stop is indeed different from stop in Studio.
Take a look in the Get Transaction Item part of the REFramework Template:
image

When you send a Stop from the orchestrator the “stop” will be picked up when the process has arrived at the “Check Stop Signal” activity.
The result of that check is stored in the boolean variable “ShouldStop”, you can probably figure out the rest from there :slight_smile:

3

@sven.wullum1,

Stopping a job/bot run from Orchestrator is a smooth way to stop bot execution. This will allow bot to finish whatever transaction is being process and then finish the execution.

Once we click on Stop from Orchestrator, it gets transmitted to bot and in Get Transaction Data, before retrieving next transaction, bot checks if there is any request to stop the execution further.

Thanks,
Ashok :slight_smile:

1 Like
4

image

when you stop a job from orchestrator this activity helps whether any stop of the job is initiated or not.
If initiated it will be set to True.

you can refer this doc for clear understanding.

5

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

3 Likes
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.