experiencing an issue with Chrome stating that no element matches

[MadhaviPathare]

Hi All,

The version of the Blue prism we are using is 6.6.0.
Both in the Production and Development environments, we are experiencing elements highlight issues.

While debugging or developing(some runs don't have any errors but the next day the error occurs on the same stage that No element matches), elements get highlighted, but they are not always working in bot runs. 

It would be helpful if you could help me find the correct solution for this. We are having a lot of problems with this type of issue in production.

------------------------------
Madhavi Pathare
------------------------------

[Vikash011]

Hi Madhavi,

I hope you are using the browser mode to spy the elements we have also faced the similar issue and changed to UIA mode.

Can you try UIA mode to spy the elements.
Please append the start page URL with the --force-renderer-accessibility parameter to open the browsers in accessibility mode. When launched using this parameter, the UIA spy mode can be used to model and interact with Chrome and Edge browsers.
Ex: https://www.google.com --force-renderer-accessibility

------------------------------
Vikash Anand
Application Development Team Lead
Accenture
------------------------------

[michaeloneil]

Hi Madhavi

When using browser mode for spying elements you need to make sure the attributes you selected are the most stable. With websites elements can be dynamic in nature so the elements you spy can be highlighted and interacted with but when you refresh the page the element may no longer be identifying since the path of the element could now have changed within the site. 

Most often if you have the path as one of the attributes selected its this part that will change within the website either a div tag/Span or a row will be different each time you visit the site. You can either try spying using a different spy mode or if you need to use browser mode try adjusting the attributes you have selected. For example possibly deselect the path and select match index. Play around with the combinations of the attributes on the element until you get the most stable identification of the element.

Hope this helps 🙂

------------------------------
Michael ONeil
Technical Lead developer
NTTData
Europe/London
------------------------------

[saivikas729]

Hi Madhavi, 

Please refer this below thread - We faced similar issue after chrome conversion. Our issues are resolved by solutions proposed by community in below thread. 

https://community.blueprism.com/communities/community-home/digestviewer/viewthread?MessageKey=f80ce2e5-1989-4ef1-b128-4054103e7cc4&CommunityKey=3743dbaa-6766-4a4d-b7ed-9a98b6b1dd01#bm5630181b-cec9-42c...


------------------------------
Kolli Sai Vikas
------------------------------