some changes

Author: lucciz01

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md

@@ -1,53 +1,58 @@
 ---
-title: Error "The remote desktop wasn't found"
-description: Solves an issue that occurs when on runtime the flow fails with 'The remote desktop wasn't found'
+title: The Remote Desktop Wasn't Found Error
+description: Solves an error that occurs when you use Remote Desktop Protocol (RDP) or Citrix automation in Microsoft Power Automate.
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
 ms.custom: sap:Desktop flows\UI or browser automation
-ms.date: 03/28/2025
+ms.date: 04/15/2025
 ---
-# Error "The remote desktop wasn't found"
+# A desktop flow fails with the "The remote desktop wasn't found" error
 
-This article helps you resolve an issue you might encounter when a flow fails with error 'The remote desktop wasn't found'.
+This article helps you resolve the issue where a flow fails with the "The remote desktop wasn't found" error when using Microsoft Remote Desktop Protocol (RDP) or Citrix automation in Microsoft Power Automate.
 
 ## Symptoms
 
-A flow using RDP/Citrix automation used to run successfully but it started failing with error 'The remote desktop wasn't found'. It might even never run successfully. This issue is more common in Citrix Virtual Apps.
+A flow using [Remote Desktop Protocol (RDP) or Citrix automation](/power-automate/desktop-flows/virtual-desktops) that previously ran successfully might start failing with the following error:
+
+> The remote desktop wasn't found.
+
+In some cases, the flow might never run successfully. This issue is more commonly observed in Citrix Virtual Apps.
 
 ## Cause 1
 
-The RDP Window/Citrix Desktop/Virtual App might changed name since when the elements were captured and tracking them with the old name fails.
+The name of the RDP window, Citrix Desktop, or Citrix Virtual Apps may have changed since the original [UI elements](/power-automate/desktop-flows/virtual-desktops#distinguish-ui-elements-captured-on-virtual-desktops) were captured. Tracking these elements with the old name can fail.
 
 ### Resolution
 
-You can repair the selectors used to retract the RDP Window/Citrix Desktop/Virtual App like normal window selectors:
+You can [repair the selectors](/power-automate/desktop-flows/repair-selector) used to track the RDP window, Citrix Desktop, or Citrix Virtual Apps as follows:
 
-1. Make sure the affected RDP Window/Citrix Desktop/Virtual App is up.
-2. Find the desktop element that has the problem in the "UI Elements" pane on Designer and double click it to open the selector editor.
+1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
+2. Locate the desktop element causing the issue in the [UI elements](/power-automate/desktop-flows/ui-elements#ui-elements) pane in the flow designer. Double-click it to open the selector editor.
 
    :::image type="content" source="media/error-remote-desktop-not-found/control-repo-desktop.png" alt-text="Screenshot of the Power Automate elements section with a Citrix desktop element highlighted.":::
 
-3. Select on "Repair" button and capture the new Desktop/App. Check the suggested changes and accept them.
+3. Select the **Repair** button and capture the new desktop or app. Review the suggested changes and accept them.
+
+   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-repair.png" alt-text="Screenshot of the Power Automate selector builder window with the Repair button highlighted.":::
 
-   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-repair.png" alt-text="Screenshot of the Power Automate selector builder window with the repair button highlighted":::
+4. After accepting the changes, select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).
 
-4. After Accepting the changes, select "Test" to test the new selector.
-5. [Optionally if needed] You can use the "New" Button to add more fallback selectors for the desktop.
+5. (Optionally) Use the **New** button to add more fallback selectors for the desktop, if necessary.
 
 ## Cause 2
 
-The usage of Citrix Virtual App with certain applications causes the creation of incorrect target desktop selector using ordinal, especially when interacting with combo box lists.
+When you use Citrix Virtual Apps with certain applications, an incorrect target desktop selector may be created using an ordinal value (for example, **eq**) instead of a more robust selection method. This is particularly common when interacting with combo box lists.
 
 ### Resolution
 
-1. Make sure the affected RDP Window/Citrix Desktop/Virtual App is up.
-2. Find the desktop element that has the problem in the "UI Elements" pane on Designer and double click it to open the selector editor.
+1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
+2. Locate the desktop element causing the issue in the [UI elements](/power-automate/desktop-flows/ui-elements#ui-elements) pane in the flow designer. Double-click it to open the selector editor.
 
    :::image type="content" source="media/error-remote-desktop-not-found/control-repo-desktop.png" alt-text="Screenshot of the Power Automate elements section with a Citrix app element highlighted.":::
 
-3. Check if the selector is using ordinal (eq is checked). If it uses, **uncheck** it and save it.
+3. Check if the selector is using an ordinal value (the **eq** is selected.) If it is, clear the value and save the change.
 
-   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-ordinal.png" alt-text="Screenshot of the Power Automate selector builder window with ordinal attribute checkbox unchecked":::
+   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-ordinal.png" alt-text="Screenshot of the Power Automate selector builder window with an ordinal attribute checkbox cleared.":::
 
-4. Click on the "Test" to test the new selector.
+4. Select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/no-clicks-on-runtime.md

@@ -1,30 +1,36 @@
 ---
-title: Elements are highlighted but on runtime clicks aren't happening on Citrix Virtual apps
-description: Solves an issue that occurs when hovering over elements in Citrix Virtual apps works but on runtime clicks don't work
+title: Can't Click Elements In Citrix Virtual Apps
+description: Solves an issue where hovering over elements in Citrix Virtual Apps works but clicking the elements during runtime don't work.
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
 ms.custom: sap:Desktop flows\UI or browser automation
-ms.date: 03/28/2025
+ms.date: 04/15/2025
 ---
-# Elements are highlighted but on runtime clicks aren't happening on Citrix Virtual apps
+# Elements are highlighted in Citrix Virtual Apps but runtime clicks on the elements don't work 
 
-This article helps you resolve an issue you might encounter when trying to click an element in Citrix Virtual apps.
+This article provides steps to resolve an issue where UI element interactions don't occur when running actions in Citrix Virtual Apps, despite the elements being properly highlighted and captured.
 
 ## Symptoms
 
-When you use the [UI element picker](/power-automate/desktop-flows/ui-elements#ui-elements-types) on Citrix Virtual apps, you're able to highlight and capture elements. However when these elements are used in an action (like 'Click Element in Window'), the interaction isn't happening and no error is shown. Test selector works fine.
+When you use the [UI element picker](/power-automate/desktop-flows/ui-elements#ui-elements-types) to interact with Citrix Virtual Apps, you can highlight and capture elements successfully. However when these captured elements are used in an action (for example, **Click Element in Window**), the interaction doesn't execute, and no error message is displayed. The [Test Selector](/power-automate/desktop-flows/test-selectors) functionality works as expected.
 
 ## Cause
 
-The Citrix Workspace HIDPI settings are interfering with PAD interactions. Mostly affected setups with multiple monitors.
+The Citrix Workspace High DPI (HIDPI) settings may interfere with Power Automate for desktop interactions. This issue is commonly observed in setups involving multiple monitors.
 
 ## Resolution
 
-1. Disable Citrix Workspace HIDPI option. From the tray icon right click on the Citrix Workspace icon.
-2. Select 'Advanced Preferences'.
-3. Click on 'High DPI' link.
-4. On the options shown, select the 'Let the operating system scale the resolution'.
-5. Click 'Save' and close the remaining Citrix workspace preferences windows.
-6. Close any Citrix Desktops or Virtual apps and start them again.
-7. If needed, change the Desktop scaling of the machine running PAD to 100%. For unattended machines follow these instructions: [Set screen resolution on unattended mode - Power Automate](/power-automate/desktop-flows/how-to/set-screen-resolution-unattended-mode)
+To solve this issue, follow these steps:
+
+1. Disable the Citrix Workspace HIDPI option:
+
+    1. From the system tray, right-click the Citrix Workspace app icon.
+    1. Select **Advanced Preferences** > **High DPI**.
+    1. In the **High DPI** settings, select the **Let the operating system scale the resolution** option.
+    1. Select **Save** and close the Citrix Workspace preferences windows.
+
+1. Close any active Citrix Desktops or Virtual Apps.
+1. Restart the Citrix Desktops or Virtual Apps.
+
+1. (Optional) Adjust the desktop scaling of the machine running Power Automate for desktop to 100%. For unattended machines, see [Set screen resolution on unattended mode](/power-automate/desktop-flows/how-to/set-screen-resolution-unattended-mode).

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/rdp-no-highlight.md

@@ -5,11 +5,11 @@ ms.reviewer: amitrou
 ms.author: nimoutzo
 author: NikosMoutzourakis
 ms.custom: sap:Desktop flows\UI or browser automation
-ms.date: 03/28/2025
+ms.date: 04/15/2025
 ---
 # UI element isn't highlighted or an error occurs when hovering over a UI or web element
 
-This article helps you resolve issues you might encounter when using the UI element picker in virtual desktops, such as Citrix or Remote Desktop Protocol (RDP) environments.
+This article helps you resolve issues you might encounter when using the UI element picker in virtual desktops, such as Citrix or Microsoft Remote Desktop Protocol (RDP) environments.
 
 ## Symptoms
 
@@ -37,9 +37,10 @@ The communication with the remote agent components doesn't work.
       > The troubleshooter can be manually opened via the console and the flow designer, through the dedicated menu under **Help** > **Troubleshooter**. It can also be opened via the process file **PAD.Troubleshooter.exe**, which can be found in the installation folder of Power Automate for desktop.
 
    1. Run **Troubleshoot UI/Web automation issues** to view the diagnostics for the communication. If an error appears in the Citrix or RDP section, expand it for more details and solutions.
-   1. If the details indicate "Access is Denied", then policies in the remote machine prohibit to run a specific agent component from the user profile folder. Contact your administrator to allow the executables to run from these directories.
 
-   :::image type="content" source="media/rdp-no-highlight/rdp-access-denied.png" alt-text="Screenshot of the Power Automate troubleshooter with highlighted the RDP/Citrix issue details.":::
+   1. If the error details indicate "Access is denied," then policies in the remote machine prohibit to run a specific agent component from the user profile folder. Contact your administrator to allow the executables to run from these directories.
+
+      :::image type="content" source="media/rdp-no-highlight/rdp-access-denied.png" alt-text="Screenshot of the Power Automate troubleshooter that shows the Access is denied error details.":::
 
 2. If the troubleshooter indicates that the remote agent isn't running, check if the agent is running in the Citrix or RDP session.
 

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/something-takes-long-and-fails.md

@@ -1,29 +1,51 @@
 ---
-title: Something takes long time and fails afterwards
-description: This article guides through the procedure that is needed to resolve an issue when interactions with RDP/Citrix applications take long and fail after some time.
+title: Operation Takes a Long Time and Fails During Runtime
+description: This article guides through the procedure that's needed to resolve an issue when interactions with RDP or Citrix applications take long and fail during runtime in Power Automate.
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
 ms.custom: sap:Desktop flows\UI or browser automation
-ms.date: 03/28/2025
+ms.date: 04/15/2025
 ---
+# Operation takes a long time and fails during runtime in Power Automate
 
-# Something takes long time and fails afterwards
+his article provides guidance on resolving an issue where operations take a long time during runtime and eventually fail in Power Automate.
 
-When trying to highlight, capture, test an element or interacting with elements on runtime, the operation takes a long time and fails afterwards.
+## Symptoms
 
-The reson for this is that there might be cases where interacting with RDP/Citrix applications might timeout and require more time to work. These time-outs can be configured like the rest of Power Automate time-outs like in [time-out configuration for UI and browser automation](/power-automate/desktop-flows/how-to/ui-automation-change-timeout-cofiguration). Use this guide to configure the following values as needed.
+When you try to highlight, capture, test an element, or interact with elements during runtime in Power Automate, you may notice that the operation takes a significant amount of time and ultimately fails.
 
-The specific configrations that need to be changed in this case are the following keys:
+## Cause
 
-- **Java.Bridge.Client.ReadWriteTimeout**: In case the target application is JAVA based, this time-out additionally increases time waiting for responses. In remote JAVA applications (RDP/Citrix), this time-out needs to be changed on the remote machine.
-- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**: In case web automation is used, this time-out increases the max time that waits for webpages to respond. In remote webpages (RDP/Citrix), this time-out needs to be changed on the remote machine.
-- **RDP.Client.CallTimeOut**: When the application/webpage is on a remote machine, either RDP or Citrix. This time-out additionally increases the max time that waits for the remote application/webpage to respond.
+The issue occurs due to default timeout settings in Power Automate that may be insufficient for certain scenarios, such as interacting with Microsoft Remote Desktop Protocol (RDP) or Citrix Virtual Apps. These timeouts may need to be adjusted to accommodate the increased time required for communication between the local and remote environments.
 
-If the problem is design oriented (for example, failing to capture an Element from the designer), you also need to configure the following too:
+## Resolution
 
-- **AutomationServerEndpoint.DesignTime.CallTimeout**: This increases the time the Power Automate Designer waits for response.
+To resolve the issue, modify the following timeout settings as needed. For more information about configuring these values, see [time-out configuration for UI and browser automation](/power-automate/desktop-flows/how-to/ui-automation-change-timeout-cofiguration).
 
-If the problem is in runtime (when running the flow), you also need to configure the following too:
+- **Java.Bridge.Client.ReadWriteTimeout**
 
-- **AutomationServerEndpoint.Runtime.CallTimeout**: This increases the max time that runtime waits for an action to be performed.
+  - Use this setting if the target application is Java-based.
+  - This timeout increases the waiting time for responses from Java applications.
+  - For remote Java applications (for example, on RDP or Citrix), configure this timeout on the remote machine.
+
+- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**
+  - Use these settings if web automation is being used.
+  - These timeouts increase the maximum waiting time for webpages to respond.
+  - For webpages in remote environments (for example, RDP or Citrix), configure these timeouts on the remote machine.
+
+- **RDP.Client.CallTimeOut**
+  - Use this setting when interacting with applications or webpages on a remote machine via RDP or Citrix.
+  - This timeout increases the maximum waiting time for responses from remote applications or webpages.
+
+## Additional timeout settings
+
+Depending on whether the issue occurs during design time or runtime, additional timeout settings may need to be configured:
+
+- For design-time issues (for example, failing to capture an element from the designer), adjust the following setting:
+
+  - **AutomationServerEndpoint.DesignTime.CallTimeout**: This setting increases the time the Power Automate Designer waits for response.
+
+- For runtime issues (for example, failing during the execution of a flow), adjust the following setting:
+
+  - **AutomationServerEndpoint.Runtime.CallTimeout**: This setting increases the maximum waiting time during runtime for an action to be executed.

support/power-platform/power-automate/toc.yml

@@ -90,24 +90,24 @@
           href: desktop-flows/ui-automation/desktop-application-crashes-ui-automation.md
         - name: Can't access the elements of a Java application
           href: desktop-flows/ui-automation/cannot-access-java-application-elements.md
+        - name: Clicking the elements don't work during runtime
+          href: desktop-flows/ui-automation/ui-rdp-automation/no-clicks-on-runtime.md
         - name: Focus window action can't bring a window to focus
           href: desktop-flows/ui-automation/focus-window-action-not-working.md
         - name: Failed to get UI element
           href: desktop-flows/ui-automation/failed-get-ui-element.md
         - name: Failed to get element/window or Element/Window wasn't found errors
           href: desktop-flows/ui-automation/ui-automation-action-fails-errors.md
+        - name: Operation takes a long time and fails during runtime 
+          href: desktop-flows/ui-automation/ui-rdp-automation/something-takes-long-and-fails.md
         - name: SAP UI element click issue
           href: desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md
         - name: Set drop-down list value in window/on web page action fails
           href: desktop-flows/ui-automation/set-drop-down-list-value-fails.md
         - name: UI element highlighting or hovering issues in virtual desktops
           href: desktop-flows/ui-automation/ui-rdp-automation/rdp-no-highlight.md
-        - name: Elements are highlighted but on runtime clicks are not happening on Citrix Virtual apps
-          href: desktop-flows/ui-automation/ui-rdp-automation/no-clicks-on-runtime.md
-        - name: Error "The remote desktop was not found"
+        - name: '"The remote desktop was not found" error'
           href: desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md
-        - name: Something takes long time and fails afterwards
-          href: desktop-flows/ui-automation/ui-rdp-automation/something-takes-long-and-fails.md
         - name: UIPI issues with UI and web automation actions
           href: desktop-flows/ui-automation/uipi-issues.md
     - name: '"Could not read the application certificate" error when creating a connection'