An existing desktop flow has been running successfully for months but this past weekend it started getting random click event errors at different places in the flow.
Our flow waits for the UI element before it attempts to click on the UI element so it’s not an issue where it is not finding the UI element. It just registers an error when it tries to click on it. And it gets these errors randomly and inconsistently at different places in the flow. Attached is a sample error.
It just seems like there must have been some update that is causing the flow to break. We did notice that Edge released an update on March 13 and was updated over the weekend on the server that the flow runs.
Has anyone else experienced similar issues with a Desktop flow that had been working? Any other thoughts on what could be causing this?
Re‑capture the UI element with the newest Edge DOM.
Add an “Ensure page is loaded” or “Wait for window content to appear” step before clicking.
Change the interaction from Click UI element → Click text / Click image (more tolerant).
Use JavaScript injection (Execute script in browser) for critical clicks instead of UI automation.
Ensure VM/server has 100% scaling, no minimized windows, and a stable display session.
If multiple Edge versions are installed → force a known‑stable version
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
4
Share
Report
All responses (
Answers (
