topic RE: Hi Kelly We just solved the… in Product Forum

Status of terminated found

KellyFarquhar — Fri, 18 May 2018 12:29:00 GMT

I'm getting a termination reason of status of terminated found. Terminating remaining sessions. I cant find any reference to the error in any documents, can someone point me in the right direction?

Hi Kelly Did you resolve…

Mustafa_UlasYig — Tue, 10 Jul 2018 14:37:00 GMT

Hi Kelly Did you resolve this issue? We are getting the same error in the schedule log viewer. Furthermore we are also getting the error ""The action was disconnected because of timeout"" (translated from Danish) in session log viewer when running directly from session management. Are you also experiencing issues with running directly from session management? We have been able to run from both session management and scheduler, but all of a sudden we cannot run anything from the control room anymore. Thanks in advance. BR, Mustafa

Hi Kelly We just solved the…

Mustafa_UlasYig — Tue, 10 Jul 2018 17:17:00 GMT

Hi Kelly We just solved the abovementioned issue. The issue turned out to be the ""named pipes"" protocol on our SQL server that was disabled. Enabling this protocol solved our problem. Hope it helps. BR, Mustafa

RE: Hi Kelly We just solved the…

Jatin__Kalra — Wed, 15 Jul 2020 10:27:00 GMT

Hi Mustafa Ulas Yigit ,

We are frequently encountering "Status of Terminated found. Terminating remaining sessions" in our control room due to which scheduler is getting terminated.
Requesting you could you please explain "The issue turned out to be the ""named pipes"" protocol on our SQL server that was disabled. Enabling this protocol solved our problem"
Please help us to resolve this issue.
Waiting for your reply.

Thanks
Jatin Kalra

------------------------------
Jatin Kalra
Assistant Manager
Genpact
Asia/Kolkata
------------------------------

RE: Hi Kelly We just solved the…

sshaw — Thu, 16 Jul 2020 06:12:00 GMT

Hi Jatin

If you have "Fail Fast" selected in a schedule, then it will terminate everything when it encounters any kind of failure. So for example, if you have a Task that is set up to start a process on 10 resources, but when running, it fails on one of those resources, it will then terminate all the other 9. If you do not want it to do this, and you want it to continue working on the other 9, then you need to unselect the option to "Fail fast on any errors".

Thanks

Sam

------------------------------
Samantha Shaw
Customer Support Manager
Blue Prism Ltd
Europe/London
------------------------------

RE: Hi Kelly We just solved the…

Jatin__Kalra — Thu, 16 Jul 2020 06:34:00 GMT

Hi Kelly,

As per your statement you mean to state that if one of my process which is having 3 tasks (task 1, task 2 and task3) which is schedule on multiple Runtime resources (R1 , R2 and R3) then if one of the resource will encounter exception ( either due to Task1, task2 or task3) it will terminate all three resources progress also.
OR you mean to say that Task2 of Resource 3 get fail it will mark Task3 of resource 3 as terminate or failure and rest two resource (R1 and R2) will work continuously independently.
OR
You mean to state that if we click " "Fail Fast" selected in a schedule" then all resources are interrelated. Which indicate if any task fails on any resource (either R1, R2 and R3) it will terminate all other resources also.
Please provide clarification.

Thanks.

------------------------------
Jatin Kalra
Assistant Manager
Genpact
Asia/Kolkata
------------------------------

RE: Hi Kelly We just solved the…

sshaw — Thu, 16 Jul 2020 06:39:00 GMT

Fail Fast affects all the processes in a single Task - https://bpdocs.blueprism.com/bp-6-8/en-us/helpTasksUI.htm?Highlight=fail%20fast

------------------------------
Samantha Shaw
Customer Support Manager
Blue Prism Ltd
Europe/London
------------------------------