Access denied if run from Scheduler

Hi,

If I try to run the robot from windows scheduler or via SSH using “UiRobot.exe execute --process NameProcess”, I get access denied. If I put this command in a bat file and run it from that file, the process starts normally. The problem only occurs with UiPath, for robots written in Python everything works fine. Any ideas?

@pikut

Does your robot which is running it has required permissions to start the job?

Cheers

@Anil_G

The script is scheduled to run from my account, which is an admin account, just like when I connect through SSH using the admin account. However, it still returns an access denied error. If I manually run the script file, it works correctly.

@pikut

May be it is using the local host instead of your user to cell the script

Cheers

Hi, I got the same issue using Windows Task Scheduler. I realized it is due to the security options. When I chose run without log on or with high privileges, I got ‘Access denied’ message. In my case, I think this option is enough for me:

Cheers,
Azeem

Why are you guys trying to run via the scheduler, the assistant has the ability to schedule robots so you can start them when you need to?

I am pretty sure the Task Scheduler is not supported.

1 Like

Hi Jon,

How can we schedule a run using the UiPath Assistant? I couldn’t find any documentation for that but only schedule a reminder.

We can actually schedule a run using Task Scheduler using UiPath CLI and it works but only for certain settings.

Regards,
Azeem

The assistant is for attended automations, so the reminders should suffice no?

Whats your use case where you intend to start an attended automation without the user prompt first?

Hi Jon,

Let’s keep this discussion respectful—I was asking a genuine question. This thread is meant to focus on UiPath CLI, not the Attended Robot per se. That said, let me clarify using a direct quote from the UiPath CLI documentation:

Attended Robots should only run under human supervision

This indicates that UiPath CLI features are applicable for Attended Robots but require the machine to remain active. This aligns with why the OP encountered an error when attempting to use it with an Unattended setup.

Regarding use cases, there are numerous complex Attended automation and background processes that demand automatic scheduling. I hope this discussion encourages further exploration of hyperautomation possibilities.

Cheers,
Azeem

I didnt realize what I asked was not respectful, it was not my intent to be disrepectful and I am not sure what part of my message you found rude.

I still believe its relevant for the discussion, because if there is a solid use case for running attended automations automatically without any user input, I think thats relevant to share with UiPath etc as their product does not currently support it.

Perhaps you can elaborate on your need, both because its important to share that requirement for future improvements and also because there might be a third option, using totally different functionality that fufills this need.

Hi Jon,

I may have made a mistake earlier, and I’d like to sincerely apologize for that. My intention was simply to respond to the OP’s inquiry. If my suggestion resolves the issue, this post can be marked as solved by @pikut.

Cheers,
Azeem