UIElement not found in Orchestrator

Help Something Else
1

Error: “UIElement not found” only when running in Orchestrator, but it is working in studio.
Thanks a lot

Forum Engagement Daily Reports
2

@Aarya_singh It will be helpful if you provide any Screen shots and are lou trying to run the process as unattended

3

@Aarya_singh

as a first step did you check the job while running or a screenshot when failed?

is the correct page and element are visible?

also what activity is it and also is selector refined?

is the screen resolution different? sometimes because of different resolution the item might not be present on the screen and might fail

cheers

4

Hi @Aarya_singh

Could you please check if element is visible while running through orchestrator try to print the element or add take screenshot activity before and after the element and verified once and if possible please send out the xaml or screenshot so I can provide you solution in better way

5

Thanks everyone for the suggestion. Yes I’m running the process as unattended. I checked the job details and the element is actually not visible in the SS that Orchestrator captured at the moment of failure the window loads differently compared to studio.

1 Like
6

Yes that the reason you are getting issue through orchestrator.

Try to indicate the selector and make selector as reliable as possible and add retry count as 3 and retry delay for 5 sec

Cheers

8

I tried taking prefailure ss and even added delays and also retry scope but the issue still persists the selector is valid but in the unattended session the element either doesn;t show up or loads partially off screen. So after applying those fixes, the robot still can’t find it.

Anything else i should check related to the unattended session settings or Ui rendering

9

@Aarya_singh

So please work towards that to see why its different..may be first time authentication screens might be different as well

if the screen is correct but element is still not visible in failed screenshot that you see then you need to change the robot resolution

cheers

1 Like
10

Please check is there any pop up windows comes while you running the bot or could you please help me with the screenshot which you are taking while through orchestrator after and before

1 Like
11

I checked that too, but still not working. Even after looking for any extra login or auth screens, the unattended session still loads differently and the element isn’t visible. i am still trying to figure out whats blocking it

12

Try to add use application browser activity and enable the restore if minimized and activated window

2, add a small delay 2-3 second before interacting with selector

  1. Increase the timeout and use wait for ready = complete

4 verify the robot machine have same version which u are using

Try this approach I hope it will resolve your issue

1 Like
13

Looks Like the unattended robot is opening the app in"Mystery Mode" in studio everything shows up pefectly , but on the robot side the UI is like, “Nope not today”

Try forcing a proper resolution in the robot settings(1920x1080). Otherwise the element might be chilling off-screen somewhere, hiding like it is avoiding work. Maximaize window also help drag it back into reality

<“Width”:1920,
<“Height”:1080,
<“Depth”:32

1 Like
14

@Aarya_singh

if it loads differently then that means there is definitely some other screen thats coming up..or the click or navigation before this is not clicking properly and its taking to a different screen..check on those lines..as clearly you are saying its a different screen

cheers

15

I tried setting the robot resolution to 1920x1080 and using maximize window, but the issue still persists. The unattended session is still loading the ui differenty from studio, and the element isnt rendered visible. i will check the othr session settings later and see if anything else is causing the ui to load differently

16

when resolution fixes dont work the main cause that the unattended session isnt intilainzing properly. u hv to enforce a consistent rdp session envioment

set this

orchestrator->robot->setting
{
LoginToConsole:false
resolution:{
width:1920,
height:1080
depth32
then add this before doing in ui
maximize window
delay 1000

then in container add
element.focus

1 Like
17

@Aarya_singh

Please try above approach and let me know if it’s work or not

1 Like
18

@manish.pal
thanks for the help!!!

19

Just see the resolution, when you are running bot in studio, check the resolution.
Set same rsolution in unattended server. This will solve your issue…

I f you are using reframework, initally you will get resolution log like Screen Resolution: 1920 x 1080
Thsi will tell you whats the resolution, accordingly set up where you want to run from orch

20

Hi @Aarya_singh

Could you please check if any of the below reason causing issue.

##1. Robot is running in a locked screen session**

If the robot runs under a locked Windows session, selectors don’t load.

  • In Orchestrator → Folders → Processes → Robot settings:
  1. Enable “Login to Console = false”
  2. Ensure “Unattended Robot” license is assigned
  3. Make sure robot starts with a fresh login (username/password configured)

2. Incorrect or too-low screen resolution

Unattended robots need a stable VDI resolution; otherwise, UI coordinates and selectors break.

In Orchestrator → Settings → Runtime rules
Set a proper resolution such as:

Width: 1920
Height: 1080
Depth: 32

or even 1366x768 if your app prefers it.

Resolution mismatch is the #1 cause of UIElement not found issues in unattended robots.

3. Application is not launched in the unattended session

In Studio, your app is already open.
In Orchestrator, the bot expects you to open every needed window.

At the start of your workflow, explicitly open the application:

  • Start Process
  • Use Application/Browser with Open
  • Wait for UI Element before interacting
  • Add delays for slow-loading apps (VDI delays are common)

4. Selectors differ between attended vs unattended mode

Some apps behave differently depending on how they are launched (Citrix, Java apps, SAP, browsers).

  • Use UiExplorer to generalize selectors (avoid volatile attributes)
  • Use wildcards for dynamic IDs
  • Use anchors where needed
  • Validate selectors by running a job in debug mode via Orchestrator

5. Robot user lacks permissions

If the robot user cannot access:

  • Application shortcuts
  • Network paths
  • Citrix/VDI clients
  • Browser profiles

selectors will fail.

Log in manually as the same robot user and verify:

  • the app can be opened
  • the robot profile has admin/required permissions
  • no pop-up dialogs (update, login prompt, security popup)

6. The app opens minimized or behind other windows

Unattended robots might open apps in the background.

Add one or more:

  • Focus activity
  • Restore Window (Invoke code if needed)
  • Use Application/Browser with Activate enabled
  • Wait for App Ready

7. Using Simulate/SendWindowMessages incorrectly

Some applications do NOT support Simulated clicks.

Try toggling these options:

  • Disable Simulate Click / Type
  • Enable SendWindowMessages
  • Or revert to Default (foreground interaction)
21

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.