Hi,
I encounter a problem with closing the windows session at the end of the process.
For example, let’s imagine that we have a process that ends with user a, when it’s time to start another process with user b, user a is still connected.
This causes problems in the applications we use. Indeed, it often happens that we have another session user than the current one who remains connected in the background.
Besides, it doesn’t happen to me all the time.
I don’t know if it’s very clear.
I feel like the orchestrator disconnects badly from the vm when it has finished processing.
Thanks
Hi @Biohazard401 ,
please check time of two process
then check other process kill browser process
regards,
LNV
Before a robot process starts, make sure that there is no existing session for the user.
If you login manually and forget to sign out from the session, robot might not be able to log out properly (you need to use sign out instead of just disconnecting the session).
Our processes are in production. Normally, we don’t need to manually connect to the vm. It is the orchestrator who manages.
Normally, at the end of the process, the orchestrator should disconnect from the vm correctly