Process stops running but does not Terminate

[StuartRedmore]

Hi all, We have very recently started experiencing an issue with processes running through Control room are in a status of €œRunning€, but when you check the log ( whilst running ) the log has stopped recording any actions, and if we remote log onto the resource to see what is taking place, the process has just €œstopped€ , the Automate.exe listener has not crashed and still shows the process as €œrunning€. It happens to different process performing different groups of actions at different times of day. The only common functionality shared by the last actions performed are: A smart wait ( various application items ) And A navigate stage with the action €œActivate Application€. ( the Application window question varies also ). Has anybody else experienced this issue and solved or does anybody have any ideas please?   Regards  

[Ravindersaini]

Hi Stuart, Are these processes on scheduler ? If yes,if a instance of a process terminates the scheduler will also stop other instances of the process running on different resource pc/ machines. Although it depends on how your scheduler is created. Regards, Ravinder Saini

[StuartRedmore]

Hi Ravinder, Thanks for the reply. Unfortunately they aren't ( though I didnt know that would cause the others to terminate anyways , so thats good to know, thanks! ), it happens when they are run manually. From research, it seems actions like ""Activate"" hand over to the application to be activated then blue prism waits for a response back, so it would appear the applications are either no passing a response back, or Blue Prism isn't picking up the response, but knowing this, doesn't leave us with anyway of fixing it, as our version Blue Prism doesn't support the timeout feature. Regards  

[david.l.morris]

That session termination feature (the one where one session termination in a task causes the others to stop) is configurable. It is on by default. Each task in a schedule has a checkbox called 'Fail fast on any errors'. If this is checked, then any sessions that fail during a run of a task will cause the other sessions to stop (not terminate). It is the same as an Immediate Stop for those other sessions. If this is unchecked, then any sessions that fail during a run of a task will not affect the other sessions.