So I have not experienced this problem before, usually the robots I have worked on have been good about waiting for SAP to load data (some t codes can take awhile to pull up information). However, I have been testing a robot I made to pull up customer invoices on a daily basis. I am about a week into testing and I have run into a problem for the first time. In this case there were a large number of invoices for this one customer so it took a little longer than usual, but SAP is clearly in a loading state. It is not guaranteed every customer I search will have invoices so I have an element exists and an if statement to work through the dialogue boxes depending on if there are invoices or not. So I ran the debug on this workflow and noticed that the workflow within a few seconds will run the element exist activity, which causes it to get stuck once SAP finishes loading the invoices, then the next activity fails due to selector problems (since it couldn’t click out of the dialogue boxes).
Any one have any idea why it suddenly isn’t waiting for SAP to load? and any suggestions? Much appreciated.
Edit: So this issue occurred yesterday evening. I ran it this morning and there were more invoices for the problem customer today than there were yesterday and yet it ran fine! Can someone suggest why it is being so inconsistent and maybe how to handle it.