Task Scheduler - process stuck is "queued" status (Windows Server 2012 R2)


We perform automation on the client server (Windows Server 2012 R2). All .xaml runs through task scheduler and everything works correctly except for one case.

The task runs at 2.30 PM every day, in case the task runs for more than 24 hours, the settings in the Settings tab are: “If task task is already running, then the following rule applies: Queue and new instance.” Unfortunately, if this happens, the task here stays stacked in queued status and does not start automatically. We only have this problem on Windows Server 2012 R2. If the same setting is done on a laptop, the task goes to the queue and when the first task is completed, the next task starts automatically.


you know if some additional settings must be made to Windows Server 2012 R2 or what is the cause of the problem?

Thank you very much,

Marek Vrtatko

1 Like

Hi @Vrtatko

Unfortunately, running your processes from Windows Scheduler is not an officially supported way of scheduling unattended processes.

It looks like the issue could be on the system side. If it is not, then it could be that newer version of Robots handle the scenario better, but it is not a guarantee.