Could not find the UI element corresponding to this selector - only in unattended

Help Studio
1

There is an existing automation that my company uses that suddenly started getting this error: Could not find the UI element corresponding to this selector. The automation is ran unattended, but when i run it attended, this error does not happen. I have tried updating the chrome browser extension, running on different unattended machines, and redoing the selector (using click, find text position/click, find ocr text position/click, click image). None of these have worked.
Any other things i can try?

2

Verify few things like
If there is any recent update to Application, Browser, UiPath extension.

If Unattended - Prod app and attended Test/sandbox app may have different selectors depends upon the app versions.

If using Image selectors - make sure resolution is same in attended and unattended bot

3

“If Unattended - Prod app and attended Test/sandbox app may have different selectors depends upon the app versions.” For this are you referring to the app it’s interacting with? It’s a website.

4

Hi @charlotte.e,

Could you try using Live Streaming to see what is actually happening during unattended execution? This can help identify issues such as unexpected pop-ups, screen resolution differences.

Please refer to the documentation below:

Thanks

5

on a high level, i understand that the robot is clicking on a UI control on a website..
pls consider doing this, try clicking using Click activity ONLY, not need to go for image click unless the UI element is not a proper HTML element.

can you put a screenshot for more clarity, no one will be able to answer a standard approach as there could 100s of reasons why it is failing in prod alone.

possible reasons:

  1. your dev/qa website instance has a different Ui element than prod instance.
  2. prod instance is taking some time to load the page or a section of the page where this element is located but due to latency at that point, it wasn’t able to find it.
  3. your selector needs to trim the dynamic attributes.
  4. the input method that you are using could be a harware event(which cannot run in background) and your website’s ui element is not in focus/ visible.

Again, screenshots on your UI element and the object descriptor details would help, narrow down the issue.

SG.

6

@charlotte.e

  1. Is the input mode hardware ? If so try simulte
  2. Also this generally occurs in unattended due to resolution differences make sure in robot settings in orch you set the same resolution as your machine where you are running attended

Cheers