Run robot using Windows Task Scheduler without using Orchestrator

robot

#1

Step 1:Open Notepad
Step 2:start “” /min “C:\Program Files (x86)\UiPath\Studio\UiRobot.exe” /file:“D:\BlankProcess\Main.xaml” /input:"{‘StartedByTaskScheduler’:true}"
Step 3:Save it as batch file (Sample.bat)
Step 4: Open Task Scheduler & Create basic task and point it out to batch file.


#2

@sasicumaar Officially confirmed uipath does not supports windows task scheduler


#3

Hi @indra

Other than running a Robot in Command line, is there any other way we can run Robot without using Orchestrator.

Thanks
Venkat


#4

Hi,
Pls search before posting a question. There are many articles about this topic.

Cheers


#5

Hi,

Thanks for sharing the article.
I tried different search criteria’s like “how to run the Robot without Orchestrator” before posting but cant find the one you mentioned.

To make it clear, my question is Uipath announced that it doesn’t support Task Scheduler anymore. One way we can run Robot is from Command line. And other than this two ways, i wanted to know is there any other way that we can run Robot without connecting it to Orchestrator.

Thanks


#6

Hi,
No problem. We are running robot using Task Scheduler without any problem despite it is “not supported”. The key is to store user name/password the robot will run under in Credential Manager as described in the post above. Otherwise no extra settings are need - same like any other unattended job.

Cheers


#7

allow me to clarify : the confusion surrounding “not supported”

UiPath supports Orchestrator - as the component of their RPA platform which is designed to schedule robots to run published processes …

Although there are/were ways to run the robot via shell console, it is pointless to seek any advice/guides or information (ya know, support) to help you achieve similar functionality that Orchestrator provides.

I would limit the scope of this discussion to that which is defined by the available UiPath documentation on command-line switches, to preserve this feature in future releases of the product … I fear that this sort of discussion could result in loss of this functionality