The element attributes obtained by rpa. windos are different from those obtained by the accessibility tool

[CracktRoops]

Reopened - this issue was closed by mistake as it was created after July 2023

[cmin764]

Good question, can you post more details about it? Like:

1. App name/binary (if not private)
2. Tasks package code (former robot)
3. What do you mean by "element lookup tool", is this Accessibility Insights? (or our helper tool windows-record)
4. And by "code runtime", do you mean the printed logs by Print Tree?

Just in case the control type suddenly changes (and a better locator using name: / id: or class: strategies is not feasible), maybe it is worth trying an alternative one with the path: strategy.

• Using path: locator strategy with Windows library
• Read more on How to inspect