Thanks John, I've figured out an alternate solution. The issue was having TabProcGrowth set in our registry was setting BP recommends was breaking our application. There were then 2 processes for the same webpage, and I was having trouble differentiating between the two to re-attach (have to detach to login to Windows Security SSO pop-up). I was thinking I could identify the process ID when I launch so I could use it to re-attach after logging in.
My solution was getting all the processes in a collection and then (looping through) attaching to each one, and checking to see if one of the elements on the homepage exists with a wait stage. If it exists, I exit the loop and continue.
