Production Unattended mode issue while running the jobs

[Snehamayi_Senapati]

Hi Team,

I need help with an issue I am facing in the Production Orchestrator. When I run the bot in unattended mode, I get the following error after some time: “The bot started running and then this error appears” (screenshot attached). Could you please help me understand what all things I need to check from the Orchestrator side and from Studio? This will help me resolve the issue in Production.

Thankyou team for your help..
Thanks ,\sneha

[vivek.nadar]

@Snehamayi_Senapati Kindly check weather you have provided the System Credential to Robot while trying to run the process in Unattended setup

[nishiijain2000 (Nishi Jain)]

Hi @Snehamayi_Senapati

Please enable simulate type for all type into activity and remove msg boxes and make sure selectors Are reliable and check the credential

Cheers

[vivek.nadar]

@Snehamayi_Senapati Secondly try to bring the target element in forground using scroll activity as some time robot cant able to identify or highlight the target element

[Snehamayi_Senapati]

i have used the credentials

[Snehamayi_Senapati]

i have used stimulate but not working as expected in the click activities

[vivek.nadar]

@Snehamayi_Senapati ok great the try to perform the second step as i suggested

[nishiijain2000 (Nishi Jain)]

Then try with the second approach which I suggested check the selector and make sure there is no message box are there on your code and check unattended license are assigned or not

[Anil_G (Anil Gorthi)]

@Snehamayi_Senapati

1. Is the robot installed in user mode or service mode? ideally it should be in service mode
2. Properly signout the user from the VM.not disconnect but signout. disconnect will leave the user session and session cannot be taken by robot
3. Make sure no pops are present like windows updates or so..they would block the application and you might see this error. disable any windows pop ups..check screenshot if you can find any issues like that
4. As per error windows session is locked are you trying to start the bot and close or disconnect the machine or minimize it?

cheers

[vivek.nadar]

@Snehamayi_Senapati Some times but is unable to identify the element event if we have provided simulate its happens with me too so try to bring the element in forground and also check weather the given setting are also applied for your robot

[sayali.p (Sayali Patil)]

Hi @Snehamayi_Senapati .
The error “Cannot bring the target application in foreground because the session is locked” means the unattended robot is trying to perform UI actions while the VM is locked / RDP disconnected.

What to check in Orchestrator

1. Unattended robot credentials

• Confirm correct Windows username + password.

2. Machine/Robot status

• Machine must be Connected & Licensed.

3. Resolution settings

• Set Resolution: 1920×1080, Depth 32.

4. Runtime availability

• Ensure your folder has a free Unattended runtime.

What to check on the VM

1. No one should be logged in via RDP.

• Sign Out, do NOT Disconnect.

2. Disable lock/sleep/screensaver settings.

What to check in Studio

1. Use Simulate Click/Type wherever possible.
2. If the XAML uses activities like Activate Window / Click, they will fail if session is locked — redesign to avoid foreground dependency.

Quick Fix

1. Sign OUT of VM → not disconnect.
2. Re-enter correct credentials in Orchestrator → Unattended Robot.
3. Set proper resolution.
4. Run the job again from Orchestrator.

Cheers.

[SorenB]

Hello @Snehamayi_Senapati

If it is an option, then you could try and record the job to check if the Windows Session is locked out, as it sounds like.

You can enable recording by editing process settings → Additional settings → Job Recording

Regards
Soren

[Snehamayi_Senapati]

Hi Anil,

Thanks for your response..
i have user mode installed Enterprise User Mode is that the reason it is not working?

[Anil_G (Anil Gorthi)]

@Snehamayi_Senapati

Yes exactly..for unattended robots to run properly robot needs to be installed in service mode

if you are admin then uninstall and while reinstalling select service mode

or reachout to your admin for installing in service mode

Robot - Service Mode vs. User Mode

cheers

[Snehamayi_Senapati]

Thankyou Anil..

Right now i do not have admin permission once i reinstall i will check and confirm you.. and i will run the process in unattended mode.

[Snehamayi_Senapati]

One more thing to cross check in Orchestrator in My folders in Users i have assigned Robot Type as unattended and roles as is this correct?

[Anil_G (Anil Gorthi)]

@Snehamayi_Senapati

attended you dont need

remaining are fine..

also go to roles tab and check if robot is present assign that as well

cheers

[Snehamayi_Senapati]

Is this correct now?

[Snehamayi_Senapati]

Hi Vivek,

Thanks for the response..

I have this settings , so do i need to do any changes here?

[vivek.nadar]

@Snehamayi_Senapati if you are using your process in any VM then its good to apply these setting