Schedule Task

[Handian_Sudianto]

Hello,

It’s true we can’t schedule to run the robot using windows task scheduler?

[Sudharsan_Ka]

Hi @Handian_Sudianto

Welcome to Community!

I think yes , We dont have UiRobot to set them in the bat file to run with windows task scheduler.

Regards
Sudharsan

[Handian_Sudianto]

Hi @Sudharsan_Ka

But if we run manually the bat file, the robot is running. So this is not bat file problem, just the task schedule problem, am i right?
If we must use orchestrator? Is the orchestrator can be work using community edition?

[Sudharsan_Ka]

@Handian_Sudianto

just onky the task schedule, am i right?

Yes ,

ANd you can use orchestrator with community edition

Regards
Sudharsan

[Handian_Sudianto]

When try using orchestrator i always got ‘there are no unattended runtimes configured on this machine’. Any idea?

[muthuraman.g]

assign unattended license to that robot machine

[Sudharsan_Ka]

@Handian_Sudianto

Checkout this
https://docs.uipath.com/installation-and-upgrade/docs/unattended-community

How To Setup An Unattended Robot In UiPath || Full Tutorial Uipath 2021 || UiPath with Jeppe

Regards
Sudharsan

[jeevith (Jeevith Hegde, Ph.D.)]

Hi @Handian_Sudianto,

Cross check you have set the right permissions on your Task in Windows Task Scheduler. The following thread has some pictures on how to use Task Scheduler. You can use your .bat file as an argument after pointing to powershell.exe

.net robot launching question

Hi @alexander.cleak, You can write a simple bat file with the following contents and save it to your desired location. “FullPathToYourUIROBOTEXE\UiRobot.exe” execute --file “FullPathToYourProcessXAMLfile\Main.xaml” The quotes are important as some paths may have spaces which bat files do not allow. In your Task Scheduler in windows you can create a basic task [image] Click ok in the first window after checking on the yellow marker. This ensures that UiRobot.exe has the required access le…

Note that the way of using UiRobot.exe has changed. We can no longer call a .xaml file directly. The project has to be packed and then it can be called like so in community edition. The Robot has to be connected to the orchestrator if not you will get this error message

A local license is required pop-up

Hi @Yogi_Gozali, Sadly this has been enforced on all levels both Community and Enterprise version. We have tested this on our instances. Airgapped automations will no longer work if the UiRobot.exe is not connected to Orchestrator. Using Task Scheduler or invoking UiRobot.exe from other programming languages, will also not work if the host robot machine is not connected to the Orchestrator. UiPath has done this to ensure that robots are linked to licenses. I am sure they found out that many…

New execute command

C:\Users\%USER%\AppData\Local\Programs\UiPath\Studio\UiRobot.exe  execute --file "C:\Users\%USER%\Documents\UiPath\_Nugets\YourProject.1.0.3.nupkg"  --input "{'in_InputDataFolder':'C:\\Users\\%USER%\\Documents\\UiPath\\InputData'}" --entry "Main.xaml"