UiElement error

Hi is it advised to use fuzzy selector? if i rcv this selector error - Could not find the UI element corresponding to this selector: [1] [2] Search failed at selector tag: [1] The closest matches found are: [64%]

@ainaasyhda try to use strict selector
@ainaasyhda
Fuzzy selector contains a top-level tag which references the target window or browser tab** . It holds attributes like title, process name, URL, window name, and others, which help you properly identify the elements you want to use in your automation projects.
It creates issue when we don’t put wild card in it to make it dynamic.

1 Like

Okay I will try it out.
Anyway, do u know why sometimes UiPath thrown selector error when running in Orchestrator, however, when rerun the process, its working and there’s no selector issue.
Do u have any idea on this behavior?

Hi @ainaasyhda

Advise to uncheck the fuzzy selector and image in the selector option window and enable the strict selectors.

In fuzzy selector it will find the duplicate elements too. In this we have to use the strict selectors then it will find the exact element.

Note : Give the Anchor for that target to achieve good indication methods.

Hope it helps!!

Yes @ainaasyhda
While use fuzzy selector it works for some time it throws the selector issues for some time.

1 Like

@ainaasyhda
Fuzzy selector contains a top-level tag which references the target window or browser tab . It holds attributes like title, process name, URL, window name, and others, which help you properly identify the elements you want to use in your automation projects.

It creates issue when we don’t make the top level tags dynamic with the help of *?.

1 Like

@ainaasyhda
RPA has some limitations and selector issue is one of them due following reason

Environment Differences: Orchestrator might have different configurations or settings compared to your local machine. These differences can affect the availability or accessibility of elements targeted by selectors. Check if there are any environment-specific factors that could be causing the selector errors.

Selector Specificity: Check the selectors used in your automation workflow. If they are too specific or reliant on dynamic attributes that might change between runs, it can cause selector errors in Orchestrator. Review the selectors and make them more robust by using wildcard characters or adjusting them to be more resilient to changes.

1 Like

@ainaasyhda I recommend fuzzy selector when you want to make a full selector.

  • Contain all the elements needed to identify a UI element, including the top-level window
    But for this you need to enable strict as well.

Thanks…if your problem solved please mark it as solution so that others can get help from it.

1 Like

Thank you for your explanation. On which environmnet we are advised to use fuzzy selector? and how actually strict selector works?

Also below is an attachment of error that i encountered. It hit error on first run however when rerun it works fine.
image

Hence, for this error, what method is recommended i use?

@mkankatala
You might consider using the Fuzzy Selector in the following environments or scenarios:

  1. Web Applications: When automating web applications, the Fuzzy Selector can be useful if the target elements have dynamically generated IDs or if there are frequent changes in the structure or attributes of the elements.
  2. Virtual Environments: When automating virtual environments, such as remote desktops or virtual machines, the Fuzzy Selector can handle variations in window titles, screen resolutions, or other dynamic elements.
  3. Legacy Applications: In cases where you are automating legacy applications with non-standard user interfaces or inconsistent element attributes, the Fuzzy Selector can help handle the variations in identifying and interacting with the elements.

Here’s how the Strict Selector works in UiPath:

  1. Selector Matching Rules: The Strict Selector uses a combination of attributes and their values to match the target element. It evaluates the attributes specified in the selector and verifies if they match the actual attributes of the element at runtime.
  2. Additional Attribute Matching: In strict mode, UiPath checks if all the attributes mentioned in the selector are present and match exactly with the target element’s attributes. This means that both the attribute names and their values need to match precisely for the element to be considered a match.
  3. Ignoring Non-Matching Attributes: In strict mode, UiPath ignores any additional attributes present in the target element that are not specified in the selector. This ensures that the selector is not overly specific and still allows for variations in other attributes.
  4. Higher Accuracy: By using the Strict Selector, UiPath aims to increase the accuracy and reliability of element identification during automation. It helps avoid false matches or misidentification of elements by enforcing a stricter matching criterion.

@ainaasyhda Did you retry it? put Retry on this.

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