topic Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications in India User Group

Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

piyushkumar07 — Fri, 18 Sep 2026 10:00:51 GMT

Hello Everyone, We have been experiencing issues with web-based applications since yesterday, where Blue Prism 7.3.1 is encountering unexpected warnings while attempting to interact with application elements. The issue is occurring across multiple bots. Interestingly, when we execute the same process/stage in our lower DEV environment, it works as expected without any warnings. At this point, we are trying to determine the potential root cause, particularly whether this could be related to the Chrome version, browser integration, environment-specific configuration, or another recent change. Environment details: Blue Prism Version: 7.3.1 Chrome Version: 153.0.8010.48 and above Impact: Multiple bots interacting with web-based applications Lower DEV Environment: Working as expected Has anyone encountered a similar issue recently? If so, I would greatly appreciate any insights, troubleshooting recommendations, or potential fixes. I am also happy to discuss the issue further and share additional details if required. Thank you in advance for your support and suggestions. Best regards, Piyush

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

naveed_raza — Fri, 18 Sep 2026 11:36:15 GMT

What is the error message ? and on which stage is coming ?

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

jeffreykmc — Fri, 18 Sep 2026 12:08:36 GMT

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 -

https://support.blueprism.com/en/support/solutions/articles/7000100939--bpe-bpngrpa-18751-sessions-hang-when-interacting-with-elements-spied-using-uia-mode-using-chrome-a

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.

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

piyushkumar07 — Fri, 18 Sep 2026 12:37:24 GMT

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.

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

piyushkumar07 — Fri, 18 Sep 2026 12:42:39 GMT

Thank you Jeffrey for your insights and feedback. we will try this out for now till BP team is investigating it.

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

naveed_raza — Fri, 18 Sep 2026 12:57:03 GMT

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 ?

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

piyushkumar07 — Fri, 18 Sep 2026 13:34:24 GMT

Hi Naveed, i am checking the process in debug mode and it is working with same chrome version.

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

naveed_raza — Fri, 18 Sep 2026 13:58:26 GMT

try to run the process directly on DEV bot and see the experience

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

naveed_raza — Fri, 18 Sep 2026 17:02:33 GMT

https://support.blueprism.com/en/support/solutions/articles/7000100939

Re: Blue Prism 7.3.1 – Unexpected Warnings with Web-Based Applications

jeffreykmc — Fri, 18 Sep 2026 17:03:25 GMT

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.