We have a scheduled robot to run on a laptop from Orchestrator online, and we have applied the right credentials for the robot.
After 20 minutes, the laptop is locked out by organization policy, and when the robot is triggered it runs a few activities while the computer is locked and stops until we manually log in, it continues.
You might have used activities and selectors in your project that require active accessibility. I’d suggest you do this:
The point of break, where exactly the bot stops working, please try to figure that out from the execution logs/orchestrator logs
Post that every activity should be followed by a log message and try to see if activity can be change to simulate type or send window messages.
The log messages would help you debug, where exactly the bot is failing.
Change one activity at a time to simulate type and run again. Once you find what works, it would be a sweet spot to change the entire automation, you might have to change certain things such as introduce find elements to add dynamic wait times etc.
Hi @Salem_Ababneh
I think whay you need to do is to stop the locking of the laptop.Because on my perspective theres a bot running on that laptop and theres no need to lock the laptap.But if you desire to changes you codes you need to change the propereties of your activities to run in to the background.