We have a Background process that runs every 5 minutes. If the Bot is not already signed into its VDI, this process will get “stuck” indefinitely trying to pull assets from Orchestrator. The job will not fault; it will just continue to seemingly “hang” in the middle of our Init State for as long as we let it.
When we sign into the VDI as the Bot and disconnect from the session, effectively leaving the Bot authenticated in the machine, the Background process works. All assets are pulled, and the job does not get stuck or hang indefinitely. It takes a matter of seconds for the job to be completed.
Currently, we’re working with Assistant 23.4.1.
Any ideas why this is happening when the Bot is not signed into the VDI & does not happen when it is signed in?
We have “Login to Console” in the Robot Settings toggled off because if we toggle it on and set it to “No,” we get the following error, and the job faults:
“Could not start executor. RDP connection failed: Message: An authentication failure aborted the connection.”