14-07-21 10:58 AM
14-07-21 11:13 AM
14-07-21 05:01 PM
15-07-21 01:54 PM
16-07-21 09:45 AM
16-07-21 09:58 AM
16-07-21 11:40 AM
So i found two fixes:
1. Adding a throttle at the beginning of the step, before the conditional wait step (i thought i had already tried this, but perhaps i had not saved the changes)
2. Adding another conditional wait step, which confirms that the window I am looking for the input in exists, after that it checks if the input exists, and the it inputs data.
I know that throttles are described as best practice, but to me it seems a bit non optimal, if i add extra seconds with each step, If the system has to processer thousands of items that does add up in the end. So i am very happy that the 2nd fix works. However, I am uncertain as to why this is needed. Could it be that as i suggested earlier, that in the short span between clicking the button to navigating to the page, and for the new window to show up (it just changes the screen in the program, so nothing you can see with your eyes) it tries to spy the element and It can't because the window does not exist?
I am happy that it works now, but would love to know exactly why it failed, so i can avoid it in the future.