Inconsistent results - timeout error storeText xpath

I want you to know this took around 7-hours over 2-days in my spare time (true love, innit).

I ran the same CSV file of 301 items, twice, outputting the results into two separate CSV files for comparison.

The script opens a web-page from the input CSV file, does some checks, and, if conditions are met, opens a 2nd website where it performs a couple of actions and saves the page’s URL, along with data from the input CSV file, to an output CSV file if conditions are met.

I ran it twice to make this comparison. Data was missing in each output file.

I’ve analysed each line of the output files and cross-referenced each discrepancy with the log-files, and discovered the following:

1st run
E225: DOM failed to be ready in 30sec: occurred 25-times

2nd run
E225: DOM failed to be ready in 30sec: occurred 15-times

They always happened when opening a tab with a URL:

2025-03-24T10:26:29.659Z - [info] Executing:  | store | 60 | !timeout_pageload | 

2025-03-24T10:26:29.864Z - [info] Executing:  | store | true | !errorignore | 

2025-03-24T10:26:30.030Z - [info] Executing:  | selectWindow | TAB=OPEN | ${varDetailPage} | 

2025-03-24T10:27:01.738Z - [error][ignored] E225: DOM failed to be ready in 30sec.
2025-03-24T10:27:01.804Z - [info] Executing:  | pause | 3000 |  | 

Data was missed during these errors and they occurred at random times both in website 1 and website 2.

Conclusion(?)
I note you chose to post your request in this thread and not the other one, E225 DOM failed to be ready in 30sec, so may I assume that you’ve been working on the timeout reached when looking for element issue?

If so, it would seem it is solved! At least in this use-case. I only saw that error in the expected places, as designed, and it behaved as expected, too.

If you need more info, holla back at yo’ dawg. Hope this helps.