some updates

Author: lucciz01

support/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error.md

@@ -2,7 +2,7 @@
 title: Failed to assume control of Edge or Chrome or Firefox error
 description: Provides a resolution to the error that occurs when running a desktop flow that has a "Launch browser" action in Power Automate.
 ms.reviewer: nimoutzo, jefernn
-ms.date: 03/28/2025
+ms.date: 04/07/2025
 ms.custom: sap:Desktop flows\UI or browser automation
 ---
 # "Failed to assume control of Microsoft Edge/Chrome/Firefox" error
@@ -65,10 +65,12 @@ Execution of a desktop flow with one of the respective actions fails with the er
 
 ### Resolution 1
 
-Increase the values of **Timeout on webpage load** and **Timeout** parameters for the "Launch new Edge", "Chrome", or "Firefox" action. For example, set these values to 120 seconds. If this adjustment doesn't resolve the issue, follow the steps outlined below.
+In the **Launch new Edge**, **Launch new Chrome**, or **Launch new Firefox** action, increase the values of **Timeout on webpage load** and **Timeout** parameters located in the **Advanced** section. For example, set these values to **120** seconds. If this adjustment doesn't resolve the issue, follow the steps outlined below.
 
 ### Resolution 2
 
+Use the Launch Browser action to start the process of the corresponding browser. Then a combination of an additional Launch Browser action with mode set to **Attach to running instance** and a [Go to web page](/power-automate/desktop-flows/actions-reference/webautomation#gotowebpagebase) action afterwards can be used to resolve the issue.
+
 1. Insert a new "Launch new browser" action as:
     - Launch new Edge
     - Launch new Chrome
@@ -108,16 +110,18 @@ Increase the values of **Timeout on webpage load** and **Timeout** parameters fo
     3. Set the interval in seconds to **5** by selecting the number of seconds.
     4. Select **Save**.
 
-6. Insert a "Go to Web page" action and set up the parameters of the action:
+6. Insert a **Go to web page** action and set up the parameters of the action:
     - Web browser instance: The variable produced by the "Launch new browser" action.
     - Navigate: To URL
     - URL: The URL you would like to navigate to.
 
-      :::image type="content" source="media/failed-to-assume-control-of-edge-chrome-firefox-error/select-parameters-in-go-to-web-page.png" alt-text="Configure the parameters of the Go to Web page action.":::
+      :::image type="content" source="media/failed-to-assume-control-of-edge-chrome-firefox-error/select-parameters-in-go-to-web-page.png" alt-text="Configure the parameters of the Go to web page action.":::
 
 ### Resolution 3
 
-Increase the values of **Timeout on webpage load** and **Timeout** parameters for the "Launch new Edge", "Chrome", or "Firefox" action. For example, set these values to 120 seconds. If this adjustment doesn't resolve the issue, follow the steps outlined below.
+Use the Launch Browser action to start the process of the corresponding browser. Then a combination of an additional Launch Browser action with mode set to **Attach to running instance** and a **Wait** action set to a duration afterwards can be used to resolve the issue.
+
+In the **Launch new Edge**, **Launch new Chrome**, or **Launch new Firefox** action, increase the values of **Timeout on webpage load** and **Timeout** parameters located in the **Advanced** section. For example, set these values to **120** seconds. If this adjustment doesn't resolve the issue, follow the steps outlined below.
 
 1. Insert a new "Launch new browser" action as:
     - Launch new Edge
@@ -141,7 +145,7 @@ Increase the values of **Timeout on webpage load** and **Timeout** parameters fo
 
       :::image type="content" source="media/failed-to-assume-control-of-edge-chrome-firefox-error/save-settings-on-error.png" alt-text="Select the Continue flow run and Go to next action options and then save the settings.":::
 
-4. Insert a "Wait" action and set its duration to 90 seconds (adjust duration as needed).
+4. Insert a **Wait** action and set its duration to **90** seconds (adjust duration as needed).
 
      :::image type="content" source="media/failed-to-assume-control-of-edge-chrome-firefox-error/wait-action.png" alt-text="Insert a Wait action with value set to 90.":::
 

support/power-platform/power-automate/desktop-flows/browser-automation/web-automation-action-fails-runtime.md

@@ -2,7 +2,7 @@
 title: Web automation action fails during runtime
 description: Provides a resolution for the issue that a web automation action can't interact with a web element on runtime in Power Automate. 
 ms.reviewer: pefelesk
-ms.date: 04/01/2025
+ms.date: 04/02/2025
 ms.custom: sap:Desktop flows\UI or browser automation
 ---
 # Can't interact with a web element on runtime
@@ -26,11 +26,11 @@ Some web pages change their underlying HTML structure dynamically. Therefore, th
 
 ## Resolution 1
 
-To solve this issue, you can try to [repair the CSS selector](/power-automate/desktop-flows/repair-selector).
+Try to [repair the CSS selector](/power-automate/desktop-flows/repair-selector).
 
 ## Resolution 2
 
-To solve this issue, you can manually create a new robust CSS selector. It will be able to locate the element of interest even though the HTML structure changes.
+Manually create a new robust CSS selector. It will be able to locate the element of interest even though the HTML structure changes.
 
 To achieve that, capture again the web element after the failure, and compare the new CSS selector with the old one.
 CSS selectors can be reviewed and edited through the **Selector builder** window:

support/power-platform/power-automate/desktop-flows/browser-automation/web-automation-unattended-failures.md

@@ -5,7 +5,7 @@ ms.custom: sap:Desktop flows\UI or browser automation
 ms.reviewer: amitrou
 ms.author: amitrou
 author: amitrou
-ms.date: 03/28/2025
+ms.date: 04/07/2025
 ---
 # Web automation action fails in unattended mode
 
@@ -25,7 +25,7 @@ This error might be caused due to the following reasons:
 
 #### The browser doesn't start and the browser window isn't visible
 
-To work around this issue, make sure that the browser start isn't blocked in unattended mode. Verify by using the actions listed and make sure that browser opens and the window is visible.
+To work around this issue, make sure that the browser start isn't blocked in unattended mode. Verify by using the actions listed and make sure that browser opens and the window is visible. To create the corresponding action, copy the following command and paste it in the [flow designer](/power-automate/desktop-flows/flow-designer).
 
 For Chrome:
 
@@ -49,10 +49,10 @@ WebAutomation.LaunchEdge.AttachToEdgeByUrl TabUrl: $'''https://www.microsoft.com
 
 To work around this issue,
 
-1. Increase the default values of the following parameters:
+1. In the **Launch new Microsoft Edge**, **Launch new Chrome**, or **Launch new Firefox** action. increase the default values of the following parameters located in the **Advanced** section:
 
-    - Timeout on webpage load (for example, set to 120 seconds)
-    - Timeout (for example, set to 120 seconds)
+    - **Timeout on webpage load** (for example, set to **120** seconds)
+    - **Timeout** (for example, set to **120** seconds)
 
 1. If increasing the timeout doesn't resolve the issue, use the following actions to obtain a browser instance:
 
@@ -66,6 +66,8 @@ To work around this issue,
 
 To work around this issue, ensure that the user running the cloud flow in unattended mode has the browser extension installed.
 
+To check the browser extension installation, you can go through the **Tools** > **Browser extensions** options in the [flow designer](/power-automate/desktop-flows/flow-designer). For more information, see [Install Power Automate browser extensions](/power-automate/desktop-flows/install-browser-extensions#install-browser-extensions).
+
 #### The machine's CPU usage reaches 100%, preventing the service worker of the web extension from starting
 
 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).