SOLVED:
A fellow developer helped me with this. So that is definitely an SAP server busy pop up, and what's happening is that blue prism is querying SAP scripting and when SAP is running a long report, it can't respond to the scripting request hence SAP has its own timeout and throws that dialog window.
Here's how I solved it. Anything you're running that may take a long time, execute it and then launch a wait stage with a LONG wait and then check if something on the page that's running (transaction screen) disappears. So object check exists = false. I originally was checking the project entry text box, however, I used SAP scripting to spy that. So, mine was failing because blue prism would lose communication with SAP and SAP would throw the server busy error as it was dedicating its resources to running my report. I then changed the blue prism wait stage to check the execution ""clock"" at the top left using AA spy mode to see when clock check exists = false (WIN32 mode was not seeing the difference between the clock and the button in the same place on the next results page, so I couldn't use WIN32), but AA was. So you use either an AA or WIN32 mode object check to see if the page finished processing and opened the results page (with a long, long wait), as AA and WIN32 operates independently from SAP scripting responses, and this WORKED!!!! No more server busy errors for me. :)
