Applies to Product - Power Automate
What’s happening?
The customer is experiencing an error in Power Automate Desktop where the flow could not launch Microsoft Edge, resulting in the message: "Failed to assume control of Microsoft Edge (communication with Power Automate web extension failed)."
What’s happening?
The customer is experiencing an error in Power Automate Desktop where the flow could not launch Microsoft Edge, resulting in the message: "Failed to assume control of Microsoft Edge (communication with Power Automate web extension failed)."
Reason:
The underlying cause of this may include: - The Power Automate web extension for Microsoft Edge is disabled or not installed. - Background processes of the Edge browser may be interfering with Power Automate Desktop's ability to launch a new instance. - Timing or synchronization issues when the bot attempts to assume control of the browser.
The underlying cause of this may include: - The Power Automate web extension for Microsoft Edge is disabled or not installed. - Background processes of the Edge browser may be interfering with Power Automate Desktop's ability to launch a new instance. - Timing or synchronization issues when the bot attempts to assume control of the browser.
Resolution:
To resolve the Power Automate Desktop error with Microsoft Edge, follow these steps: 1. Check the Power Automate Web Extension: Ensure that the Power Automate web extension is installed and enabled in Microsoft Edge. If it is not enabled, check with the IT team as it may be blocked by organizational settings. 2. Reinstall the Extension: If the extension is installed but not functioning, remove it and reinstall it. After reinstalling, restart the browser. 3. Terminate Background Processes: Use a "terminate process" action at the start of the desktop flow to kill any Edge processes running in the background that may interfere with launching a new instance. 4. Launch Browser with "about:blank": Instead of launching directly to a specific URL, first launch the browser with the "about:blank" page, and then navigate to the required URL. 5. Verify PAD.BrowserNativeMessageHost.exe: Ensure that PAD.BrowserNativeMessageHost.exe is running for Microsoft Edge. If it is not running, check the installation and enablement of the Power Automate web extension. 6. Implement Error Handling: Insert an error handling policy in the flow to manage errors effectively. Set the flow to continue running to the next action in case of an error. 7. Adjust Timing: If the issue persists, consider adding a delay before the bot attempts to focus on elements within the browser to ensure the page is fully rendered.
By following these steps, the issue with the Power Automate Desktop and Microsoft Edge should be resolved. If the problem continues, further investigation may be required.
To resolve the Power Automate Desktop error with Microsoft Edge, follow these steps: 1. Check the Power Automate Web Extension: Ensure that the Power Automate web extension is installed and enabled in Microsoft Edge. If it is not enabled, check with the IT team as it may be blocked by organizational settings. 2. Reinstall the Extension: If the extension is installed but not functioning, remove it and reinstall it. After reinstalling, restart the browser. 3. Terminate Background Processes: Use a "terminate process" action at the start of the desktop flow to kill any Edge processes running in the background that may interfere with launching a new instance. 4. Launch Browser with "about:blank": Instead of launching directly to a specific URL, first launch the browser with the "about:blank" page, and then navigate to the required URL. 5. Verify PAD.BrowserNativeMessageHost.exe: Ensure that PAD.BrowserNativeMessageHost.exe is running for Microsoft Edge. If it is not running, check the installation and enablement of the Power Automate web extension. 6. Implement Error Handling: Insert an error handling policy in the flow to manage errors effectively. Set the flow to continue running to the next action in case of an error. 7. Adjust Timing: If the issue persists, consider adding a delay before the bot attempts to focus on elements within the browser to ensure the page is fully rendered.
By following these steps, the issue with the Power Automate Desktop and Microsoft Edge should be resolved. If the problem continues, further investigation may be required.