We are currently investigating a known issue affecting browser automation in Power Automate for Desktop (PAD) when running automations against Google Chrome versions 146 and 147.
In specific scenarios, browser automation actions may fail to interact with the intended web UI element, leading to inconsistent or unexpected behavior during flow execution.
Issue details
When using certain browser automation actions with physical interaction enabled, Power Automate for Desktop may not correctly target the intended element on a webpage when automating Google Chrome version 146 or 147.
As a result:
• An unintended element on the page may be selected
• The mouse cursor may move to an unexpected location on the screen
• Desktop flows may behave inconsistently or fail
• Previously working automations may break after upgrading Chrome
This issue impacts all supported versions of Power Automate for Desktop when used with the affected Chrome versions.
When does the issue occur?
The issue occurs only when physical interaction with the web UI element is enabled in a browser automation action, where applicable.
Specifically, the following actions may be affected:
• Populate text field on web page
When Populate text using physical keystrokes is set to True
• Click link on web page
When Send physical click is set to True
• Hover mouse over element on web page
When Move mouse to hover is set to True
• Extract data from web page
When Send physical click for next page is set to True
Workarounds
Recommended workaround
As a temporary mitigation, downgrade Google Chrome to version 145, where the issue is not observed.
To downgrade Chrome on Windows, follow the guidance in Manage Chrome updates (Windows) and review the downgrade instructions carefully.
When following the article, pay particular attention to:
• Step 1, which is required before proceeding
• Step 3, section ‘Roll back Chrome browser to a previous version’
This workaround should be considered temporary until a permanent fix is available.
Alternative workaround
If your automation scenario allows it, you may also avoid using physical interaction options and rely on non-physical browser automation where possible, until the issue is resolved.
Current status
This issue is under active investigation. We are working to identify the root cause and will provide updates as more information becomes available.
