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
------------------------------