Object recognition for chrome is inconsistent for a particular web application

[jessiebrooks]

I'm using Blue Prism  6.10.1.35171.   We have a very dated web based application that we are automating. It was automated in version 6.8 but we still had some issues.    Our current issue is as follows:

We can spy all web elements in Chrome  and Edge.
We can debug the automation in an interactive session.
We can run the process from Control center on a machine we've connected to via RDP.

If we run the process on a machine we've not connected to directly we have issues recognizing objects. 

I've added manual waits to try and account for pages loading longer but this doesn't seem to help.   

We are running on virtual machines and using Windows 2019.  The Virtual Machines we use to develop automations and run them are built from the same image.    

We have other automations using the same version of Windows and Chrome working on other web applications.    Any ideas would be greatly appreciated Thanks!


------------------------------
Jessie Brooks
------------------------------

[HarpreetKaur]

Hello Jessie,

A few things that come to mind are:
1. Do you use login agent to connect to the machines ensuring they're available before a process can run on them?
2. Are you seeing similar results across all machines or is it particular to a few?
3. What do the logs say for the the failed automation process? Is it erroring our at a single step?
4. Are you using Attach stages for all your objects?
5. Instead of manual waits can you try using Intelligent waits with the CheckExists feature?
6. Is it the entire automation that does not run at all from the start or are there bits and pieces involving just the browser parts?

If you could share the error message that would help.

------------------------------
Harpreet Kaur Product Consultant
------------------------------

[jessiebrooks]

Excellent Questions.

1. Do you use login agent to connect to the machines ensuring they're available before a process can run on them?
Yes  and we wait 120 seconds before we start the automation. 

2. Are you seeing similar results across all machines or is it particular to a few?
Yes.  We even built a new VM to rule out something on the old VMs

3. What do the logs say for the the failed automation process? Is it erroring our at a single step?
The logs all indicate the process was not able to find the object.  For example

ERROR: System Exception : System Exception: Unable to navigate to customer maintenanceFailed to perform step 1 in Navigate Stage 'Navigate to Customer Search' on page 'Customer Maintenance Search' - No element matched the query terms

4. Are you using Attach stages for all your objects?
We attach before each page in the object. 

5. Instead of manual waits can you try using Intelligent waits with the CheckExists feature?
We've tried all versions of the built in wait stages in addition to custom loops to "wait again" just in case

6. Is it the entire automation that does not run at all from the start or are there bits and pieces involving just the browser parts?
Typically starting the browser and navigating to the application along with the login work without issue.   Everything past that seems to be the problem

Overall  the entire automation will work if someone is actually watching it.

------------------------------
Jessie Brooks
------------------------------