topic Re: Random Termination in Product Forum

Random Termination

ChrisBrook — Fri, 22 Jan 2021 12:48:43 GMT

Hi,

Hoping someone can help. We have a process which launches an web application via IE11.

For some reason, the first time the process is triggered from the schedule after a login we get a termination. However there are no exceptions or errors in the log (full logging enabled).

Control Room:

I've covered the process names however you can see that we sucessfully login, the process runs and then terminates. I then retrigger the schedule (run now) which causes the login agent to fail but then the process itself works fine.

Log (from failed process run):

You'll see that the last log entry is on the 'Launch' action but with absolutely no exception/ error informatio what so ever.

It also doesn't bubble up back to the process main page and follow the termination steps; even though it's designed to.

Any thoughts?

Chris

Re: Random Termination

NicholasZejdlik — Fri, 22 Jan 2021 15:37:36 GMT

Is it possible there's not enough lead time after the login? The Login Agent service remains active until the Blue Prism software has launched on the robot. So after logging in, if you immediately send a process to the robot, I believe it would be getting run by the Login Agent service. If that's the case, it could explain why the log is getting cut off without an exception, since the Login Agent would terminate after the Blue Prism software loads.

Re: Random Termination

ChrisBrook — Fri, 22 Jan 2021 15:47:15 GMT

@Nicholas Zejdlik - that's a good shout.
I have it set to 5 seconds but I'll look to extend it to a minute and see what happens tomorrow - cheers.

Re: Random Termination

John__Carter — Mon, 25 Jan 2021 09:46:19 GMT

The name of the Login process can be misleading. The job of the process is only to pass credentials to Windows, it doesn't wait for the user to be fully logged in and the desktop to be ready. If the scheduler assigns another process immediately after the Login process, then it's likely that Windows will still be transitioning from a 'logged out' to a 'logged in' state. Adding a schedule pause after Login acts as a buffer to give the machine time to settle into the 'logged' in state.