I’m reaching out regarding an issue we’re experiencing with Task Scheduler.
Straight to the point:
We currently execute some of our bots using Task Scheduler. However, several end users have reported that they are not receiving the confirmation emails with the reports that should be sent after each robot execution. This is a red flag, as it’s definitely not normal behavior.
Here’s what’s happening:
Four of our scheduled tasks are not being triggered. This occurs at various times—midnight, early morning, and even while I’m present.
I’ve tried different command formats to execute the UiPath automation:
execute -file
execute --file
-FileAll of these were researched in the forums, but none of them are being executed automatically by Task Scheduler. However, when I double-click the .bat file directly, it works perfectly regardless of the command format used.
In Task Scheduler, under the Last Run Result column, some tasks show as completed, while others display the error code (0xFFFFFFFF).!image|213x500
I’m aware that we could use Orchestrator, but the current model was implemented using Task Scheduler due to specific requirements.
I’ve recreated the tasks, enabled “Run with highest privileges”, and configured them to stop the task if it exceeds the expected runtime, to avoid affecting subsequent executions.
Any ideas or suggestions would be greatly appreciated?
Researching across this multiverse of possible solutions:
One of the solution is publish the process without orchestrator directly to the “PACAKGE FOLDER”, where all the nkpg are saved. Some of my automation ran succesfully, however other not.
Two with the “EXECUTE” method other automatios are still working well, but is so weird that just a group is working with packages and other not.
Also I tried to use method with scheduler, where we used the path where is located de UIROBOT and passed an argument. This one for me not works, just with a test automation with only message box inside in it. However, when I tried to pass the BAT file as argument, is not working.
Then, I am stuck why because for the thre methods, some robots acept one of them. And the other not.
Please confirm that the account you are using to trigger task scheduler tasks have admin privileges?
As per my understanding, if you don’t have admin privileges, you need to be logged onto the machine when task scheduler run is triggered for its successful execution.
The account we are using to execute the tasks does not have administrative privileges.
However, we are using two laptops that are always logged in. Our structure model is as follows:
My PC can access any of the VMs via RDP or using RDCMAN.
During the shift, I am the person behind the session. This means the robots are triggered through RDCMAN, allowing for an attended session during the day.
On the other hand, during the nights, is different I call all the robots to another laptop, but this one is located in a server room.
Now let me tell you I applied this during the weekend.
One of my group of robot are working now with nugget packages, and the other with execute commands.
Only one of my robots are not working with any of the method, is showing me right now “ACCES DENIED”
Whats the main reason you are choosing to do this via the Task Scheduler and not from the Orchestrator?
Its my understanding that the Task Scheduler is no longer supported as a method to run automations from UiPath. You should have everything you need if you trigger from the Orchestrator for unattended processes, and if you want an attended the assistant also has a scheduling function that will be able to remind users to start it.
It should resolve any issues with packages aswell as give you centralised logs to use.
But for the moment the model my boss wants is this.
The method I am using is publish the package of the project (nkpg), and after of this, create a BAT file, and using UiRobot to execute the file. For the moment is working well.
I really appreciate your opinion and i’ll check the assistant solution you told me.
So I found that an interesting answer, so I read your other topic.
Am I correct in surmising that you have an attended robot, and you are running it this way via the Task Scheduler so you can trigger automations to run throughout the night?
Is important to check that in task scheduler you don´t have the check box for RUN WITH PRIVILAGE, in cases like me, where my IT team or security team can´t grant those permissions. Reason, because during the execution through CMD, you will receive a error saying ACCES DENIED.
If you want to see a message error un your CMD, at the of the script inside to the BAT file add the command PAUSE, it will be pausing the CMD windows and you can see the error or messages that appears during the execution.
I used to method thar are working for me right now. One is create the package of the project, using the pusblish method but locally. Once is created we need to create tehe BAT file, but instead using the command EXECUTE use this
The other method is the one you know that exist, that in some of my bot are still working well
My advice with task scheduler also is whe you are setting up a task, please in the SETTINGS tap, use the check box called STOP THE TASK IF IT RUNS LONGER THAN: there you need to add a time it has a default list but you can type minutes as well. This to stop the task whe is taking more of the time you assign. In my case I noticed that per default appears 3 days, and that stuck the process and most of the time it doesn´t allow to execute the other tasks.
I suspected as such because using the task scheduler this way is usually a red flag to me that someone is trying to bypass the licencing terms of the attended licence, or misuse a free community licence commercially.
I have bad news. You are breaking the licence terms in my opinion, so must stop doing this immediately.
Using attended robots in this manner, so they run unattended without human supervision, is I believe a violation of your contract. It has been this way for a long time and the licence terms for an attended licence do indicate it requires human supervision.
There is a post here from back in 2020 where someone from UiPath also clearly clarifies, the manner you use this licence is not allowed.
I strongly urge you to stop this immediately. Escalate this to your manager and your UiPath contact and explain the error, and upgrade to an unattended licence. I am assuming this is a honest mistake based on historic misunderstanding and not deliberate but hopefully this is clear now.
