Kill Process and Stop Process in Orchestrator

Help Orchestrator
,
1

Hello,
In Orchestrator, under the Jobs Tab, we have Stop Process and Kill Process options against each job. I understand that Kill process will terminate the BOT with immediate effect. But what does Stop Process performs in addition that Kill process can not do? In real time, I see both terminates the BOT immediately. I couldn’t figure out the exact difference. Can any one help please?

Thanks.

2

@shahidh.aqeel.shahul

check this thread

3

Hi @shahidh.aqeel.shahul

Stop Process:

  • What It Does: Tries to end the job in a controlled way, allowing it to finish up what it’s doing and clean up properly if possible.
  • When to Use: Use it when you want the job to stop but also want it to finish its current task or close things safely.

Kill Process:

  • What It Does: Immediately stops the job without letting it clean up or finish its current task. It’s like pulling the plug.
  • When to Use: Use it when the job is stuck or not responding, and you need to stop it right away, even if it means it won’t close things properly.

Regards,

1 Like
4

Hi @shahidh.aqeel.shahul ,

Stop Process - Will stop the process in a controlled manner. What it means is that whenever a stop command is issued from the orchestrator, the bot will not stop the job immediately. Instead, it will continue running until it encounters - Activities - Should Stop, and then it will terminate the workflow.

In the RE Framework, you can find this in the Get Transaction Item. So, the bot will not stop abruptly in the middle of the execution of a transaction item. Instead, it will end gracefully after completing the current transaction.

The image depicts a UiPath workflow sequence for getting transaction data, checking a stop signal, and deciding whether to stop the process or continue retrieving transaction data. (Captioned by AI)
The image depicts a UiPath workflow sequence for getting transaction data, checking a stop signal, and deciding whether to stop the process or continue retrieving transaction data. (Captioned by AI)982×732 119 KB

Kill Process - Will terminate the process abruptly.

Hope it helps…

Regards,
Ranjith Udayakumar

5

Hi Ranjith,

Thanks for the explanation. I have two points here. Can you please help?

  1. In RE Framework, if the BOT is currently processing a transaction item in “Process Transaction” state and we stops the process from orchestrator, the entire transaction item will be processed and completed. Then on entering “Get Transaction Data”, it is going to be stopped at the “Check Stop Signal” activity. Is this correct?

  2. In case of customized framework, if we do not have the ‘Check Stop Signal’ activity, how the stop process from Orchestrator will work?

Thank you…

6

Hie @shahidh.aqeel.shahul kill process is used when you want to stop the process on immediate effect … like it does’nt care about the process or while you are working with reframework if kill process is execute it kill the process even your transaction item is on processing.and your bot is running
while stop process is first complete the running process or transaction item if they are in process and after completing the running process then it should stop the process
cheers Happy Automation

7

Hi Sumit,

Can I come with an example here. Lets say, in Process transactions, they are 10 steps.

Now, BOT enters into process transaction for one transaction item. Stop process is clicked when the BOT is executing step 1 in process transition. So, is it like, BOT will execute the remaining 9 steps inside the process transaction for the current item and then stops?

Is my understanding correct?

9

In UiPath’s REFramework, if you click “Stop Process” while the BOT is executing a transaction item in the Process Transaction state, the behavior is typically as follows:

Immediate Effect of “Stop Process”

  1. Immediate Halt: When “Stop Process” is clicked, the BOT will attempt to stop execution immediately. This means that the BOT will not continue executing the remaining steps of the current transaction item.
  2. Current Step Execution: If the BOT is executing Step 1 of a transaction item and you click “Stop Process,” the BOT will stop its execution right away. It does not wait to complete the remaining steps (Steps 2 through 10) of the current transaction item.
  3. Transaction Integrity: The transaction will remain incomplete, and the steps that have not been reached will not be executed. This is important to handle in your workflow, as you may need to manage incomplete transactions appropriately.
10

Hi Sumit,

So, Stop process is also stopping the execution immediately. This is where I’m getting confused with Kill process since kill process is also stopping immediately.

11

@shahidh.aqeel.shahul

  • Stop Process: Sends a signal to the BOT to stop as soon as possible, allowing it to attempt to finish the current task or transaction gracefully. It is less disruptive but may not always complete the current process.
  • Kill Process: Forcibly terminates the BOT or process immediately, without allowing for any graceful shutdown or completion of tasks. It is more abrupt and can lead to incomplete transactions or other issues.
    this is the major difference hope you get the point now.
12

@singh_sumit okay… Got it. Thank you…

1 Like
13

@shahidh.aqeel.shahul Your most welcome… :smile: :smile:

1 Like
14

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