Technically yes but I thought it is prohibited using scheduler if it is unattended robot.
is there any official notes by uipath team?
I once heard it from uipath sales staff, you’d better to ask them. Also, here we have license training, it might help you.
Hi, The official link that mentions about the support for Task Scheduler: https://www.uipath.com/kb-articles/how-to-schedule-a-task
Currently, For an unattended Robot triggering them from the Orchestrator is only supported.
Hi @Dominic @Jumbo @Abisha
The kb-articles are deprecated and not actual.
Regarding Task Scheduler… it’s not prohibited anyway we are not supporting it anymore. It’s the reason why Orchestrator has been made.
Thanks for your help, I got it.
In that case, can I run attended robot with task scheduler even if there is nobody around the PC? (like mid night scheduling?)
I though I heard “attended robot without operator does not allowed”…
As said by others windows task schedular is not supported
Rather we got the options to trigger a process in a scheduled base with Orchetsrator Schedule option
Here is the official confirmation with the documentation of that process
it is only for enterprise version right?
As I wrote KB-Articles are not supported anymore. Soon those will be removed as are not actual and deprecated. Scheduling has been unsupported as in newer Studios/Robots they might be not compatible or throws and errors. It’s no that we don’t like this solution or anything like that.
How would you like to perform task scheduler with attended robot on locked machine when user session is locked or logged off? According to this:
Attended - works on the same workstation as a human user and is usually triggered by the user through their actions (user events). You cannot start processes 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 Prompt. Attended Robots should only run under human supervision.
No in general
it applies to both edition
Thanks for your reply. I mentioned about this: Attended Robots should only run under human supervision.
I mean the PC is not logged off for robot execution but no one there. I think that is prohibited as you mentioned.
But “should” doesn’t mean “prohibited” . I just wanted to say that it might not work, or the effect will be not as wanted. This is all about why we are not supporting it. If somebody want to try, sure . But we can’t solve any issues/errors related to this based on the fact that Orchestrator has been made for scheduling
I got it. now I’m clear
If I have chance, I will try the task scheduler way.