in VM i have made a workflow to extract data and send it via mail everyday , So i have published the flow to orchestrator and have an unattended bot for this but still when it is getting triggered and my laptop is off it is getting failed but when my system is on it is getting successful;
, Plese let me know to resolve this issue
If your laptop is off, bot did not have valid machine to run on. so it fails.
If you want it to run you have to keep it powered on.
Also You can use Cloud™ Robots - VM
Your unattended bot fails when your laptop is off because the UiPath robot runs on your laptop’s machine. When the laptop is powered down or asleep, the robot cannot execute the workflow, causing the job to fail. To fix this, you need to install and connect the UiPath robot on a machine that is always turned on, such as your virtual machine (VM). Make sure the VM stays powered on and connected to the internet. Then, in Orchestrator, schedule the job to run on the robot that is linked to your VM, not your laptop.
For more:
setup was done on a VM, which is AD Enabled , when i am triggering the process manually and disconnecting from the VM the process is getting paused and then it is getting germinated after a couple of mins
Schedule trigger on VM at specific time, and disconnect from VM before process run started. After run you can relogging to VM and just watch.(It’ll work if VM allow multiple user login at a time).
Tried that but it is getting failed
so pls let me know if any other solution
Pls share the screenshot of error message
When you say you are disconnecting from VM.
Do you mean you logged into VM and simply disconnected?
If yes, it holds back the license if you don’t sign out.
Kindly sign out of the VM and then kick start the process from orchestrator. Robot will automatically login to the VM and run the process.
Make sure to set “login to console” as no in robot setting on orchestrator.
Is the robot installed in service mode?
You should not shutdown but only signout
Cheers
what exactly is a service mode? i am just closing the VM directly
not signing out, so basically if i am closing it is getting signout
When you install robot it asks for user mode or service mode
To check now open task manager go to services/details tab and check if you see UiPath.service.host ..if yes then good if no you need to uninstall and install again in service mode
Now coming to closing its not good practice click on start button select the person icon and select signout
Cheers
so maybe i was closing directly it was showing that error in orchestrator?
because when i am running manually through orchestrator it is getting success , when i am doing through time trigger it is getting success when the UI is visible in VM but when i am not in VM it is showing faulted in orchestrator
Disconnecting from the VM is not same as signing out from the VM.
Disconnecting holds the license.
Kindly sign out from VM, if you are looking to NOT see the process in action.
And then run from orchestrator, it would work.
Please note below:
- when you want to run from orchestrator and see the process in action, stay logged in to the VM. Don’t disconnect.
- when you want to run from orchestrator but don’t wish to see the process in action, Sign out so bot can login and complete the process.
if i am doing sign out then it is showing that it is in pending state and no machile is allocated
what exactly is installing robot?
You mentioned your workflow is published to Orchestrator and you are using an unattended robot on a VM, but you also said that when your laptop (system) is off, the job fails.
This suggests that the robot is running on your local laptop—not truly on the VM. Or, your VM requires an active session (RDP session open) to process the task.
- The Robot is Registered to Your Local Machine (Laptop), not the VM
Verify: In Orchestrator under Robots/Users > Machines > Robots, confirm which machine the unattended bot is assigned to.
Mark solution if its help
Let’s take a step back.
Kindly confirm below
-
in your orchestrator folder from where you are running the process, you have your VM assigned to that folder? Also you have your unattended robot assigned to that folder as well?
-
please check the robot settings under manage access, have you provided login credentials for that robot to be able to login to that VM? And provide setting like resolution and login to console?
-
when you say VM, you are not referring to your local machine, right? Which machine did you sign out from? Did you login to that VM using Remote Desktop connection from your local machine and then signed out of that rdp connection?
So when you open the UiPath msi file it asks if you want to install robot or studio…there you need to select robot and unattended
Cheers
so my whole flow is there in VM, and orchestrator is also there in VM .so if my VM is opened then trigger is running fine,