Restrictions of attended robot

We understood that the attended robot can be run by the tray or the command line.
Will it breach the license agreement if we put the command line to a .bat script and register to the windows scheduler?
We will log when the robot is being called and the result in the script, can it be considerred as the supervision of the robot operation, or this is prohibit by UiPath license agreement?
Or we have to use unattended robot with Orchestrator?

– We have several processes doing by RPA but some of them takes a long time so want to be run doing night time but check the result the next morning.

1 Like

@dengfeng

There is no such limitation as of now.

@dengfeng

We didn’t hear anything like this from UiPath yet

Hope this helps

Thanks

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Hi @dengfeng
For a technical perspective, you can wrap the command line with a .bat script and execute using Windows Scheduler. However, from a license agreement perspective this would be a violation of the terms of usage of Attended Robots.

In our documentation (https://docs.uipath.com/robot/docs/according-to-license), the following are stated:

Attended - operates on the same workstation as a human, to help the user accomplish daily tasks. It is usually triggered by user events. You cannot start a process from Orchestrator on this type of Robots, and they cannot run under a locked screen. They can be started only from the Robot tray or from the Command Promp. Attended Robots should only run under human supervision.

Usually the purpose of executing robotic processes using Windows Task Scheduler is to remove dependence on manual triggering or manual intervention and therefore the robot is NOT running under human supervision in which case could be considered as violation of the mandate for attended robots to be running under human supervision.

If you want to schedule the execution of your robotic processes my suggestion is to use Orchestrator + Unattended Robot.

2 Likes

Hi @Matthew_Tan,
Thank you for your comments. As it would be more costly to have the Orchestrator and unattended robot. And the frequency to run the robot is low but want to be at a certain time. Is there any other solutions?

Hi @Matthew_Tan,
I’m naoto, colleague of dengfeng.
Now we’re considering the following scenario, instead of using windows scheduler.

User remote login to the robot PC
-> Manually launch the robot
-> Disconnect the remote desktop service before the robot complete the process
-> Receive the result by mail sent by robot.

Will this idea be a licence policy violation?
Wondering if supervisor has to be in front of robot PC until the end of process not going anywhere…

Hi @naoto.yagi
I suggest you speak to the Account Executive from UiPath assigned to your company regarding this matter.