cancel
Showing results for 
Search instead for 
Did you mean: 

Stopping a session from Control Room

Anonymous
Not applicable
What's the difference between those three commands

34051.jpg



------------------------------
Sanaa Fallah
------------------------------
1 BEST ANSWER

Helpful Answers

Hi Sanaa,

The difference between 'Immediate Stop' and 'Request Stop' is that when you use 'Immediate Stop' the session is going to terminate exactly at that point of the instance when you click on it no matter where your point of execution is currently at. Better way to stop the process is 'Request Stop' but to use this you need to have a Decision Stage in your process where you can use the expression: 'IsStopRequested'. What it essentially does is whenever you click on this button, the process won't be killed immediately but infact will stop only when the flow comes to this exact decision point. We generally put this decision after completing a particular transaction by making the queue item as Completed or as Exception so that we can ensure that the process is stopped safely. When you use 'Immediate Stop' a lot of unwanted errors can happen depending on what the bot is actually doing at that point of time. For example, if the bot is writing some Excel file and you click 'Immediate Stop', then doing so might result in the corruption of that file as we ended the process abruptly. Hence, as a best practice it is always recommended to use 'Request Stop' instead of 'Immediate Stop'.


However, as certain situations when let say your Automation is running in an infinite loop or your process doesn't reach the decision stage where 'IsStopRequested' is being used, 'Request Stop' functionality won't work. In such a situation, 'Immediate Stop' can be used so that you can stop the session and troubleshoot the errors.

------------------------------
----------------------------------
Hope it helps you and if it resolves you query please mark it as the best answer so that others having the same problem can track the answer easily

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------
---------------------------------------------------------------------------------------------------------------------------------------
Hope this helps you out and if so, please mark the current thread as the 'Answer', so others can refer to the same for reference in future.
Regards,
Devneet Mohanty,
SS&C Blueprism Community MVP 2024,
Automation Architect,
Wonderbotz India Pvt. Ltd.

View answer in original post

4 REPLIES 4

Hi Sanaa,

The difference between 'Immediate Stop' and 'Request Stop' is that when you use 'Immediate Stop' the session is going to terminate exactly at that point of the instance when you click on it no matter where your point of execution is currently at. Better way to stop the process is 'Request Stop' but to use this you need to have a Decision Stage in your process where you can use the expression: 'IsStopRequested'. What it essentially does is whenever you click on this button, the process won't be killed immediately but infact will stop only when the flow comes to this exact decision point. We generally put this decision after completing a particular transaction by making the queue item as Completed or as Exception so that we can ensure that the process is stopped safely. When you use 'Immediate Stop' a lot of unwanted errors can happen depending on what the bot is actually doing at that point of time. For example, if the bot is writing some Excel file and you click 'Immediate Stop', then doing so might result in the corruption of that file as we ended the process abruptly. Hence, as a best practice it is always recommended to use 'Request Stop' instead of 'Immediate Stop'.


However, as certain situations when let say your Automation is running in an infinite loop or your process doesn't reach the decision stage where 'IsStopRequested' is being used, 'Request Stop' functionality won't work. In such a situation, 'Immediate Stop' can be used so that you can stop the session and troubleshoot the errors.

------------------------------
----------------------------------
Hope it helps you and if it resolves you query please mark it as the best answer so that others having the same problem can track the answer easily

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------
---------------------------------------------------------------------------------------------------------------------------------------
Hope this helps you out and if so, please mark the current thread as the 'Answer', so others can refer to the same for reference in future.
Regards,
Devneet Mohanty,
SS&C Blueprism Community MVP 2024,
Automation Architect,
Wonderbotz India Pvt. Ltd.

KodiSrihari
Level 8
Hi @Sanaa Fallah,

Stop Selected Sessions :- This will stop the selected session  from the Environment ​that is currently running ,as per requirement by business. This will update status against                                                  the session as Stopped. 

Request Stop   :-  This will stop the session after completing the current Queue Item that it picked if in Running state .It will complete current ticket and stop.

Immediate Stop :-  This will stop the current running Process in what state it might be i.e if running a ticket it will stop.

Thanks,

------------------------------
Srihari
RPA Developer
------------------------------

Anonymous
Not applicable

@devneetmohanty07

So 'Stop Selected Sessions' works as same as 'Stop Immediately?



------------------------------
Sanaa Fallah
------------------------------

@Sanaa Fallah - Yes that's right, using this functionality you can immediately stop multiple sessions at once. It works as 'Immediate Stop' not 'Request Stop'​

------------------------------
----------------------------------
Hope it helps you and if it resolves you query please mark it as the best answer so that others having the same problem can track the answer easily

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------
---------------------------------------------------------------------------------------------------------------------------------------
Hope this helps you out and if so, please mark the current thread as the 'Answer', so others can refer to the same for reference in future.
Regards,
Devneet Mohanty,
SS&C Blueprism Community MVP 2024,
Automation Architect,
Wonderbotz India Pvt. Ltd.