Kill failed runtime windows sessions

[JosepArques]

From time to time, a runtime process ends in a non-controlled way, so runtime process ends but the windows session that was executing the process remains. Because of this, loginagent cannot start again and the resource appears as offline. The only way to make the resource available again is by ending or killing the windows user session that was executing the runtime process. Has BluePrism any way to stop or cancel a windows session when runtime process crashes?

[david.l.morris]

Hi, Do you have an example of one of the non-controlled ways that the session terminated? Ordinarily, whether a session (running process instance) finishes as expected or terminates, the resource should return to a status of Idle (or some simiilar message). Respectfully, Dave

[JosepArques]

thanks for your answer Dave, with non-controlled I mean when Automate.exe crashes for any reason.

[John__Carter]

You shouldn't be getting any automate.exe crashes, it's far from normal. I'd recommend contacting the support team.