I have a UiPath process running on a Windows server under a specific robot user. The process is triggered via Task Scheduler and is also visible in Orchestrator. It performs UI automation in a desktop application (clicks, get text, etc.).
The execution starts normally. I can see logs in Orchestrator at the start and end of the offer creation step. However, the UI actions are not happening unless I reconnect to the robot’s session using RDP.
I monitor the process from a separate local desktop (not through RDP). I can see that the number of offers waiting to be processed is not decreasing. When I connect to the robot machine via RDP, the robot resumes the automation immediately. For example, it clicks on button A, then I disconnect the RDP session, and 10 minutes later, when I reconnect, it’s still on the same screen. Only after the RDP session is re-established does it continue with the rest of the actions.
During the disconnected period, Orchestrator shows the process as running and logs are being written, but the UI is clearly not responding.
It looks like the robot is running in a non-interactive or locked session and UI automation doesn’t actually work until a user session is active.
How can I make sure that the robot runs in a proper interactive session even when no one is connected via RDP? Should I change settings like LoginToConsole in Orchestrator?
How can I check if the robot is installed in Service Mode?
Regarding the logs – yes, they appear normal. For example, when the process starts creating an offer, the log says something like registruojamas ne web užsakymas, and once it’s done (after all related activities are completed), I get užregistravo ne web užsakymą. So from the logs it looks like the process is executing correctly and not stuck, even though in reality the UI actions don’t seem to happen unless I’m connected to the session.
Additionally, I added a log entry with "UserInteractive = " + Environment.UserInteractive.ToString
and even when I’m disconnected from RDP, it still logs True.
I found out another topic with the same problem. Regarding your first question, I put a powershell script looking like this:
$servicename = "UiRobotSvc"
if (Get-Service $servicename -ErrorAction SilentlyContinue) {
Write-Host "$servicename service exists -> That means the robot is installed in Service Mode (Unattended Robot)."
Get-CimInstance -ClassName Win32_Service | Where-Object Name -eq 'UiRobotSvc' | Format-Table -Property ProcessId,Name,DisplayName,StartMode,State,Status -AutoSize -Wrap
} else {
Write-Host "$servicename not found -> That means the robot is installed in User Mode (Attended robot) or not installed at all."
}
I got the output : UiRobotSvc not found → That means the robot is installed in User Mode (Attended robot) or not installed at all.
Hi @Povilas_Jonikas , I ran into the exact same issue recently. as @Anil_G have pointed out, it turned out our Robot wasn’t installed in Service Mode. In your case, since your Orch settings look correct, all you need to do is reinstall studio and choose the service mode installation option.
Its also a bad idea to run from the Task Scheduler, the Orchestrator can start automations any time you want using a Time Trigger, and manage the jobs better (in case of overlapping jobs for example).
If you get the Service Mode installed properly, it will ensure the user can log in, run the automation without any ‘monitoring’ and close on its own.
What led you to try to schedule this via the task scheduler?
Ok guys, so I have just completed installing UiPath into service mode and tried running the process again. But, sadly, the same thing. I keep getting logs, that the automation is “running” and doing all the things it needs to do, but i can see in a different window, that the unregistered offers in my program stays the same, when they should be going down in numbers one at a time.
Could there be something wrong with my orchestrator setup? Maybe I have done something wrong with the creation of the tenant or something? Or maybe the RDP session is wrong and something needs to be done? Your help is highly appreciated.
The most likely culprit, is that you attempted again to run from the task scheduler.
Can you run it from the Orchestrator, as a normal unattended automation, and let the robot log in itself etc.
As I asked before, what led you to try to start automations via the scheduler and not the intended way in the Orchestrator?
Hello Jon and thanks for the answer. I have all my automations put on task scheduler, because sadly, I dont believe that my orchestrator is setup normaly. If I try to run a task with orchestrator triggers, it doesnt start. I need to give some time and configure orchestrator like it should be configed. And actually thats where im heading at. If this process on RDP works, my company will buy UiPath licenses and try to work only thorugh Orchestrator.
This time I ran it thorugh Assistant, not task scheduler. My task scheduler is setup like so, that it would trigger an action, which just opens the Assistant automation shortcut. So in some way, all the automations are working through Orchestrator, just that not from its triggers, but from task schedulers. Like now, i have ran the autoamtion that i need to run properly on RDP session:
Also when you say task scheduler is starting are you not signing out the user at all?
Ideally better include some screenshots at random places and check the current state of the UI that might shed some light as ideally if actions are not performed atleast it should fail unless continue on error is checked for all activities
Ideally if not run from orchestartor the process is not unattended at all
No, the robot is not in offline mode. It’s connected to Orchestrator, and robot status shows as available.
I do not sign out the user. The RDP session is disconnected using a .bat script that runs tscon, so the session remains active and unlocked.
Continue on error is not checked on all of the activities. Ill add activities to screenshot the UI and share them as soon as possible.
Now when im tryint to setup a trigger on orchestrator for this process, i select Hostname - the same host that is on RDP connection, but I get a message Hostname is unresponsive, even tho im connected to it now and i see that assistant is connected and its shining green (STATUS: Connected, Licensed). Im even logged in to the orchestrator on RDP through web.
If I understand you correctly, then yes. This process that im trying to run unatended has some clicks, get text activities, and use application/browser. Basic process but it has a lot of meaning in my company day to day work.
So if you mean ‘Free Plan’
It doesnt allow you to run unattended automations.
If you mean ‘Community’ that shouldnt be considered ‘free’, its strictly for non-commercial use, and you indicated above you were using it for your company commercially.
Either way it seems you are violating the licence terms, which is also likely why you are having so much trouble here.
If I am right, you need to stop running automations on the licence you have, your are violating the TOS you signed and its not legal.
You can sign up to the basic plan for $25 per month if you already used a professional trial.
Please stop these workarounds however. All the issues you face I believe are caused by trying to misuse the licences.
Free version is not supposed to be used for productions
If its free version/community version may i know how did you install in service mode as that is not allowed at all
Ideally any uanttended automation needs to be triggered from Orchetsrator and the rdp needs to be signedout so that robot signs in , but in your case you are trying to run like an attended bot which is unattended
Did you happen to give robot role to a. user only then it would be visible
Also unattended license needs to be given to machine and I believe you already have given it as I see the machine selection is happening in Orchestrator
Now coming to issue try to check screenshots as mentioned to know the current state and move forward with issue. Also its really weird to know that logs are correct but no ui actions are happening as it cannot be the case unless the website is having all elements active even if nothing is being done
Oh, ok guys. Thanks for the insights. Ill go and buy a plan, reconfigure my robots, machines and ect. Reinstall the UiPath then and will try again. Will come back to you in a bit if nothing has changed. Thanks a lot!
I asked a couple of times, but was there a specific resource you found suggesting the ‘task manager’ route?
I see it many times and it always seems to be a suggestion used to attempt to bypass licencing terms, if there are tutorials or something advocating it, I’d like to know so we can try to get it removed.
To be honest, I didn’t find any official or community resources online that suggested setting up robot runtimes or automation triggers through Task Scheduler. At the time I started with UiPath, the Orchestrator setup felt like a lot to take in — I was a complete beginner, didn’t have any coding background, and even the basics of how automation tools work were new to me.
Although I always intended to do things properly through Orchestrator, it just felt too complex early on. After I built my first working process, I tried many times to trigger it through Orchestrator — I needed it to start at 6:30 every morning, repeat every 2 hours, and run for about 12 hours a day. But no matter what I tried, Orchestrator wouldn’t trigger the process. I checked schedules, robots, folders, permissions — everything I could think of — and still couldn’t figure out why it wasn’t working.
Eventually, I tried running the published Assistant shortcut via Windows Task Scheduler — and that worked. So I went with it, not as a way to bypass anything, but simply because I couldn’t get the Orchestrator setup working properly at the time and I needed a practical solution.
Even now, I’ll be honest — I still don’t know how to use Orchestrator fully or correctly. But I believe it’s about time I figure it out and start doing things the right way. I appreciate all the input and guidance you’re giving — it’s helping me move in that direction.