UiPath Studio 2025 vs. Windows 11 Task Scheduler issue

Help Community
1

I faced an issue about running Studio job through Windows 11 Task Scheduler. It’s a very simple Studio project that likes “Hello World” as attached zip file. And as what we expected, it runs successfully through Studio workbench.
But when I scheduled it as a job through Windows Task Scheduler, it seems like that the Studio had not invoked, because nothing pop-up. Is here anyone having any comments on this issue?
following is Windows bat file content:
start C:\Users...\AppData\Local\Programs\UiPath\Studio\UiRobot.exe execute --file "D:...\MyHelloWorld\Main.xaml
MyHelloWorld.zip (2.6 KB)

Forum Engagement Daily Reports
2

This is stated in the documentation:

The following commands are not supported for Windows or cross-platform projects:
UiRobot.exe execute --file “C:\UiPath\Automation\Main.xaml”
UiRobot.exe execute --file “C:\UiPath\Automation\Project.json”

So unless your project is Windows Legacy (which I doubt) you can’t run XAML file.

Cheers

1 Like
3

As I understand it, running via Task Scheduler is not supported by Studio.

The intended options are, for an unattended automation, running via triggers in the Orchestrator.

For attended automations, running via the assistant, the assistant has a calendar feature which can remind you to start a scheduled automation at a specific time if you want.

1 Like
4

Hi @Caesar ,

I use the below batch script, and it works for me, and our runs every day via task scheduler:

start " " /min “C:\Program Files\UiPath\Studio\UiRobot.exe” execute --file “D:…\MyHelloWorld\Main.xaml” /input: “{‘StartedByTaskScheduler’: true}”

I have made the above few lines bold which are different than your bat script.

If your UiRobot.exe present in and Program Files or Program Files(x86) then better use that one.

In your bat script I can see that double quote(" ") is missing:
Missing quote C:\Users…\AppData\Local\Programs\UiPath\Studio\UiRobot.exe
Expected “C:\Users…\AppData\Local\Programs\UiPath\Studio\UiRobot.exe”

Try fixing the quote mistake of try the batch script I have provided.

If it resolves your issue. Please mark this as a solution.

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.