Give us back the good selector not found errors

Feedback Activities
,
1

So the modern design activities are great, and I have had a positive experience with the switch.
I have one major complaint however, the error messages that replace the ‘SelectorNotFound’ are trash.

Previously I’d get a great error telling me what the selector was and then the percentage matches on similar matches that it found, it was awesome. I could often debug a bad selector by only looking at the error.

In modern design I get this error

Could not find the user-interface (UI) element for this action.

Possible solutions:
• Ensure application is opened and the UI element is visible on the screen at execution time
• Edit the Target of the UI activity and use Validation to debug the issue.
• If needed, re-indicate the element as its properties might have changed
• Use “Check state” activity to check the application state before executing the action
• Increase the “Delay before” value to allow time to the application to render entirely and become responsive

Its really quite useless at helping me debug, my only choice is to try to edit the selector in question, flip over the Ui Explorer and see what I can do. If you have this on a production machine or as an intermittent issue well, tough luck.

Please improve this error, I don’t think suggestions such as suggesting I use “Check State” are appropriate in an error message, just give me the information I need to correct the debug the error like the previous equivalent error did.

2 Likes
5

@uipath can this feature be added back to the modern activities?
Having the exact information about on what part of selector bot failed was really helpful with developments, as sometimes bot fails only in unattended mode and we are unable to verify/understand where exactly it is failing.

6

Exactly, I could often tell what to fix simply by looking at a log message, its now much harder.

You can turn on extra logging with Modern design which shows the progress of the competing selectors, but I still want the clear error message back.
Put it in the data dictionary in the error for all I care, just give it back please.