Selector Works Fine Then Suddenly Fails After Windows Update - aaname Changed

How to make selectors resilient to Windows updates that change UI element properties? Should I remove aaname from selectors entirely and use other attributes, or use wildcards for all text-based attributes?
What’s the best practice for production bots to survive OS updates without breaking?

@Rohit_Chaurasiya,

aaname property don’t get changed due to OS update. It’s updated by the Desktop or Web Application update.

Check the changes and make your selectors as flexible as possible by avoiding idx, dynamic properties and values.

You can also leverage Healing Agent to auto recover and quick fix selector for the UI changes.

Hi @Rohit_Chaurasiya,

Use wildcards in selectors - change aaname=‘Submit’ to aaname=‘Submit*’ or remove aaname entirely.
Prioritize stable attributes: automationid, name, class over text-based attributes like aaname.
Use Anchor Base to find elements relative to stable nearby elements.
Enable fuzzy matching in selector properties for text attributes.
Add selector validation during bot initialization to catch failures early before processing starts.
This makes selectors resilient to Windows updates.​​​​​​​​​​​​​​​​

Thanks & Happy Automation

1 Like

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