Inconsistent results - timeout error storeText xpath

This was a painful exercise, taking several hours over a couple days, not including writing this today.

I ran the same macros using v.6.2.8 and v.9.3.8 (the latest) in Chrome. There is one macro which calls another; both run against two different websites, respectively.

Below are screenshots of the CSV output files.

Image 1 - v.6.2.8:

  • all items were successfully retrieved on first attempt.
    output-v.6.2.8

Image 2 - v9.3.8:

  • multiple attempts (delineated by red lines) with varying results. The last attempt retrieved all results successfully.

(Note: the black line is to hide an entry that was recently added to the list - it can be ignored.)

Some other attempts, not shown here, retrieved nothing at all.

Clearly, the results are wildly inconsistent.

Errors

The log-file recorded two errors that repeatedly blocked data collection. They did not occur at the same time.

  1. E225 DOM failed to be ready in 30sec
  • This error can happen on both websites.
  1. timeout reached when looking for element ‘xpath=//rt-table-cell[3]/div/span[2]’
  • This happens only in the second website.

I am only addressing the second timeout error in this thread, although both together compound the issue.

In operation, sometimes the element is on the page, sometimes an additional couple of clicks in a side-panel are needed to update the table. It doesn’t matter, it can still fail in either scenario. I have tried a different xpath route with the same, inconsistent result.

Only because I was physically watching it did I suspect something was not right. And only by re-running it in v.6.2.8 could I isolate the issue to v.9.3.8. Otherwise I might have falsely concluded the run had successfully completed when in fact lots of entries were missed.

Users should beware of the last sentence.

Do you have a test macro for us? We would love to run this and debug it further. Despite adding lots of computer vision and AI features recently, we are well aware that the classic web automation remains the backbone of Ui.Vision.

As you probably know, Version 6.2.8 is the last version using Manifest 2. This often allowed for a much more direct automation. With manifest v3 things got a lot more involved, requiring additional internal steps to achieve the same.

My offer to work with you on this (for free) still stands if we can make it happen (E225: DOM failed to be ready in 30sec - #3 by TheWhippinpost).

It seems this may still be symptomatic of several stubborn issues that’ve lingered for several years whilst migrating UI.Vision to Manifest 3.

From a personal PoV, I am concerned now that the temporary fix in Chrome to continue running Manifest 2 extensions will end mid next year; ie, v.6.2.8 will cease to work.

From a wider PoV, this could be affecting users who are unaware that their data-collection is missing data.

I will do my best to accommodate you in the new year if you can make it happen.