Skip to content

Update web-automation-unattended-failures.md #1961

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
learn-build-service-prod merged 1 commit into from
Nov 6, 2025
Merged

Update web-automation-unattended-failures.md #1961

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...automate/desktop-flows/browser-automation/web-automation-unattended-failures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,8 @@ To check the browser extension installation, you can go through the **Tools** >

To work around this issue, provide more CPU resources to the machine where the flow is executed. For more information, see [Prerequisites](/power-automate/desktop-flows/requirements#prerequisites).

Starting with version 2.62, Power Automate for desktop supports [WebDriver](https://learn.microsoft.com/en-us/power-automate/desktop-flows/actions-reference/webautomation#webdriver-based-browser-automation-preview) as an alternative communication method for browser automation. WebDriver provides a more resilient communication channel that does not rely on the browser extension.

### Scenario 2: Other web automation actions fail with the "Element not found" error

The following web automation actions might fail with the "Element not found" error:
Expand Down