I have 2 unattended automations that are using a dispatcher and performer model using REFramework with queues.
Previously this was working without error when triggering the job manually. However now I am noticing that when the job runs it seems to be stuck in a state where it is waiting for the execution to start. When I want to view the logs of the job while it is running, there are no logs to display. This makes me suspect that it is not reaching the step to run the workflow. The bot is using a VM to do the job and the machine status is indicating a green light as connected based off of the heartbeat.
I need some guidance on where to troubleshoot since I didn’t modify the workflows. The package versions are up to date for both performer and dispatcher. My suspicion is that something in Orchestrator is causing this point of failure. Thank you again!
I’m not sure when the last time the VM was restarted, but based off of the post you linked it appears to be a similar problem. The main difference is I don’t believe I am getting the error that the robot’s session is already active on another machine.
This timeout issue can occur sometimes when there is a delay in making the connection.
It has happened for us as well few times, but usually starts working after sometimes.
For us, UiPath had suggested to move 24.10.6 as it had better ability/prolonged time period to try to make connection before actually timing out.
We have also noticed that sometimes when the VM disk space is quite full or temp folder is quite full, then also we have faced this issue, so clearing the space also helps.
Now coming back to your original issue, I would suggest to follow the steps they have followed in the post and see if it makes any difference for you.
Also to see if any user session is active on that VM, do below
Go to tenant-> monitoring-> user sessions → this will show you if on your particular VM(under hostname), any else user session is active or not.
It looks like restarting the VM helped! The automation is now running as expected. Thank you for pointing me in the right direction. A lot of company stress has been avoided.
Yes, it indeed is a good idea to restart VMs regularly. It helps in offloading data from past service runs and with any updates on the machine.
You can even consider creating an admin automation to restart your VMs regularly (weekly, daily, biweekly or monthly) whatever works for your organization.
