Unable to trigger and execute a UiPath process via a time-based trigger created

Help Orchestrator
,
1

unable to trigger and execute a UiPath process via a time-based trigger created in UiPath Orchestrator in Unattended mode. The process fails to run when scheduled, despite the robot being available and configured.

2

@Aditya_Nalawade11,

What error do you get?

3

The workflow runs perfectly in attended robot mode, but as soon as it switches to unattended mode, it stops working.

4

Hi @Aditya_Nalawade11

Is it showing any error in the logs while running the workflow from orchestrator…?

Could you be more specific.

5

Whenever i m closing my RDP/VM unattened Robot stop

6

Hi @Aditya_Nalawade11,

Does it stay in Pending state or it runs but throws error?

Regards
Sonali

7

An error message indicating that the target application cannot be brought to the foreground because the Windows session is locked. (Captioned by AI)
error Message

8

Hi @Aditya_Nalawade11,

I suspect your robot is installed in user mode.

It has to be in service mode for run in unattended mode and also your robot needs to be configured with credentials in the orchestrator to be able to login to the machine.

Please refer below post for more details:

Regards
Sonali

1 Like
9

How to check Robot is in User mode or service Mode?

10

@Aditya_Nalawade11,

To check if a UiPath robot is installed in User Mode or Service Mode,
1)Go to start menu and open the Windows Services console by searching for “services.msc”
2)and look for the “UiPath Robot” service;
3) if the service is present, the robot is installed in Service Mode,
4)if not, it’s in User Mode

Regards
Sonali

1 Like
11

@Aditya_Nalawade11,

Alternatively, you can also refer steps mentioned in the below post for same:

Regards
Sonali

1 Like
12

Robot is in Service Mode just checked

13

@Aditya_Nalawade11,

Okay thanks for confirming.

Can you go through below post and cross check all the points mentioned in there? There can be the case that some settings are not in place correctly for you.

Regards
Sonali

14

Okay @Aditya_Nalawade11

Install the robot in Service mode. Then this will sort the issue

If installed in user mode the bot will not able to execute in the foreground untill screen opens.

Follow the below video to setup unattended mode,

Hope it helps!!

1 Like
15

Tried everything still facing same error

16

Hi @Aditya_Nalawade11,

Can you confirm if you are logged out of machine/VM? If not, can you try doing that and then run automation from orchestrator?

Regards
Sonali

17

Shall i logout ?? from VM

18

Hey @Aditya_Nalawade11

If you are facing issues in installing robot in service mode in VM, follow the below video @RAKESH_KUMAR_BEHERA have explained how to install robot in service mode.

Hope it helps!!

19

@Aditya_Nalawade11,

Yes, as you have already checked and confirmed about the service mode and all other settings being in place, I think you should try to log out of the machine/VM where you want to run unattended process and then run it from orchestrator.

Please note: Don’t disconnect. Signout.

Regards
Sonali

20

The image shows a Windows Start menu with options to disconnect, shut down, or restart, alongside a search bar and shortcuts for Microsoft Edge, File Explorer, and Google Chrome. (Captioned by AI)
The image shows a Windows Start menu with options to disconnect, shut down, or restart, alongside a search bar and shortcuts for Microsoft Edge, File Explorer, and Google Chrome. (Captioned by AI)587Ă—213 10 KB

No log out option