yesterday
yesterday
What is the error message ? and on which stage is coming ?
yesterday
My guess is that you are running into the issue as seen here with the latest version of Chrome and processes that utilize elements spied in UIA mode -
I assume maybe you don't see this in your dev environment as you are actively monitoring/stepping through the process, which oddly enough appears to resolve/sidestep the issue. Hopefully BP will have an update soon. For now, you'll need to roll back to an earlier version of Chrome or utilize a non-UIA mode solution.
yesterday
Hi Naveed, error logs are not coming it is getting stuck at navigate stage and going to warnings usually same piece of code was working in DEV and was working in PROD from last 1 years.
yesterday
Thank you Jeffrey for your insights and feedback. we will try this out for now till BP team is investigating it.
yesterday
Okay, if you are using UIA mode then try with different spy mode as suggested by Jeffrey and also you can try re-spying the element.
another question, are you testing the process by running in debug mode in DEV or running the process directly on DEV Bot ?
yesterday
Hi Naveed, i am checking the process in debug mode and it is working with same chrome version.
yesterday
try to run the process directly on DEV bot and see the experience
yesterday
yesterday
In my testing, if you have the process active on your screen/active virtual desktop window, it will work properly. If it is working unattended, it will get stuck. I just watched it pass by a spot its having an issue with and as long as the HVD window was active, it did not have a problem.