25-06-21 09:39 AM
We have this weird issue which occurs once in a while, where a chrome automation does not start until the user logs onto the machine. As soon as the user logs in, automation continues and finishes.
This is a random behavior as most of the time, automation executes as expected according to the schedule. Anyone else dealt with similar issues? We thought an upgrade to 6.10.1 would fix this, but we're still seeing the same issue.
25-06-21 11:56 AM