Skip to content

Commit 37732b6

Browse files
authored
Merge pull request #8598 from iopanag/users/iopanag/RDP-docs
AB#5226: Added troubleshooting docs for Power Automate RPD/Citrix automation
2 parents 13dc378 + 353e86e commit 37732b6

File tree

9 files changed

+168
-3
lines changed

9 files changed

+168
-3
lines changed
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: The Remote Desktop Wasn't Found Error
3+
description: Solves an error that occurs when you use Remote Desktop Protocol (RDP) or Citrix automation in Microsoft Power Automate.
4+
ms.reviewer: amitrou
5+
ms.author: iopanag
6+
author: iopanag
7+
ms.custom: sap:Desktop flows\UI or browser automation
8+
ms.date: 04/29/2025
9+
---
10+
# A desktop flow fails with the "The remote desktop wasn't found" error
11+
12+
This article helps you resolve an 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.
13+
14+
## Symptoms
15+
16+
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:
17+
18+
> The remote desktop wasn't found.
19+
20+
This issue is more common in Citrix Virtual Apps.
21+
22+
## Cause 1
23+
24+
The names of the RDP window, Citrix Desktop, or Citrix Virtual Apps might 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.
25+
26+
### Resolution
27+
28+
To solve this issue:
29+
30+
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
31+
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.
32+
33+
:::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.":::
34+
35+
3. Select the **Repair** button and capture the new desktop or app. Review the suggested changes and accept them. For more information, see [Repair a selector](/power-automate/desktop-flows/repair-selector).
36+
37+
:::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.":::
38+
39+
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).
40+
41+
5. (Optional) Use the **New** button to add more fallback selectors for the desktop.
42+
43+
## Cause 2
44+
45+
When you use Citrix Virtual Apps with certain applications, especially when interacting with combo box lists, an incorrect target desktop selector might be created using an ordinal value (for example, **eq**) instead of a more robust selection method.
46+
47+
### Resolution
48+
49+
To solve this issue:
50+
51+
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
52+
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.
53+
54+
:::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.":::
55+
56+
3. Check if the selector is using an ordinal value (the **eq** is selected.) If it is, clear the value and save the change.
57+
58+
:::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.":::
59+
60+
4. Select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).
61+
62+
[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Operation Takes a Long Time and Fails During Runtime
3+
description: Solves an issue where interactions with Remote Desktop Protocol (RDP) or Citrix applications take a long time and fail during runtime in Power Automate.
4+
ms.reviewer: amitrou
5+
ms.author: iopanag
6+
author: iopanag
7+
ms.custom: sap:Desktop flows\UI or browser automation
8+
ms.date: 04/29/2025
9+
---
10+
# Interactions with RDP or Citrix applications take a long time and fail
11+
12+
This article provides guidance to resolve issues where operations take a long time to run and eventually time out. It describes the settings that can be modified to accommodate longer timeout periods.
13+
14+
## Symptoms
15+
16+
When you try to highlight, capture, test a [UI element](/power-automate/desktop-flows/ui-elements), or interact with UI elements during runtime in Power Automate, the operation might take a significant amount of time and ultimately fail. This issue occurs when interacting with Microsoft Remote Desktop Protocol (RDP) or Citrix applications.
17+
18+
## Cause
19+
20+
The default time-out settings in Power Automate might be insufficient. The time-outs might need to be adjusted to accommodate the increased time required for communication between the local and remote environments.
21+
22+
## Resolution
23+
24+
To resolve the issue, modify the following keys as needed. For more information about configuring the values, see [time-out configuration for UI and browser automation](/power-automate/desktop-flows/how-to/ui-automation-change-timeout-cofiguration).
25+
26+
- **Java.Bridge.Client.ReadWriteTimeout**
27+
28+
- Use this setting if the target application is Java-based.
29+
- This time-out increases the waiting time for responses from Java applications.
30+
- For remote Java applications (for example, on RDP or Citrix), configure this time-out on the remote machine.
31+
32+
- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**
33+
- Use these settings if web automation is used.
34+
- These time-outs increase the maximum waiting time for webpages to respond.
35+
- For webpages in remote environments (for example, RDP or Citrix), configure these time-outs on the remote machine.
36+
37+
- **RDP.Client.CallTimeOut**
38+
- Use this setting when interacting with applications or webpages on a remote machine via RDP or Citrix.
39+
- This time-out increases the maximum waiting time for responses from remote applications or webpages.
40+
41+
## Other time-out settings
42+
43+
Depending on whether the issue occurs during design time or runtime, the following time-out settings might need to be configured:
44+
45+
- For design-time issues (for example, failing to capture an element from the designer), adjust the following setting:
46+
47+
- **AutomationServerEndpoint.DesignTime.CallTimeout**: This setting increases the time the Power Automate Designer waits for a response.
48+
49+
- For runtime issues (for example, failing during the execution of a flow), adjust the following setting:
50+
51+
- **AutomationServerEndpoint.Runtime.CallTimeout**: This setting increases the maximum waiting time during runtime for an action to be executed.
52+
53+
[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]
Loading
Loading
Loading
176 KB
Loading
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Can't Click Elements in Citrix Virtual Apps
3+
description: Solves an issue where hovering over elements in Citrix Virtual Apps works, but clicking the elements during runtime doesn't work.
4+
ms.reviewer: amitrou
5+
ms.author: iopanag
6+
author: iopanag
7+
ms.custom: sap:Desktop flows\UI or browser automation
8+
ms.date: 04/29/2025
9+
---
10+
# Elements are highlighted in Citrix Virtual Apps, but clicking them at runtime doesn't work
11+
12+
This article provides steps to resolve an issue where UI element interactions don't work when running actions in Citrix Virtual Apps, even though the UI elements are properly highlighted and captured.
13+
14+
## Symptoms
15+
16+
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.
17+
18+
## Cause
19+
20+
The Citrix Workspace High DPI (HIDPI) settings might interfere with Power Automate for desktop interactions. This issue is commonly observed in setups involving multiple monitors.
21+
22+
## Resolution
23+
24+
To solve this issue, follow these steps:
25+
26+
1. Disable the Citrix Workspace HIDPI option:
27+
28+
1. From the system tray, right-click the Citrix Workspace app icon.
29+
1. Select **Advanced Preferences** > **High DPI**.
30+
1. In the **High DPI** settings, select the **Let the operating system scale the resolution** option.
31+
1. Select **Save** and close the Citrix Workspace preferences windows.
32+
33+
1. Close any active Citrix Desktops or Virtual Apps.
34+
1. Restart the Citrix Desktops or Virtual Apps.
35+
36+
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).
37+
38+
[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]

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

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ ms.reviewer: amitrou
55
ms.author: nimoutzo
66
author: NikosMoutzourakis
77
ms.custom: sap:Desktop flows\UI or browser automation
8-
ms.date: 03/03/2025
8+
ms.date: 04/29/2025
99
---
1010
# UI element isn't highlighted or an error occurs when hovering over a UI or web element
1111

12-
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.
12+
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.
1313

1414
## Symptoms
1515

@@ -38,6 +38,10 @@ The communication with the remote agent components doesn't work.
3838
3939
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.
4040

41+
1. If the error details indicate "Access is denied," policies on the remote machine prohibit running a specific agent component from the user profile folder. Contact your administrator to allow the executables to run from these directories.
42+
43+
:::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.":::
44+
4145
2. If the troubleshooter indicates that the remote agent isn't running, check if the agent is running in the Citrix or RDP session.
4246

4347
Check the tray icon for the agent icon when the virtual desktop platform is active. If the icon exists, hover over it to confirm it's still running. If it is, right-click the tray icon to open the menu and select **Status**. The agent's status and the reason for the error will be displayed.
@@ -65,11 +69,13 @@ The communication with the remote agent components doesn't work.
6569
Set the **Virtual channel allow list for DVC** policy with the following values:
6670

6771
- `C:\Program Files (x86)\Power Automate agent for virtual desktops\PAD.RDP.ControlAgent.exe,Microsoft.Flow.RPA.Desktop.UIAutomation.RDP.DVC.Plugin,PAD\CONTROL`
68-
72+
6973
- `C:\Users\*\AppData\Local\Microsoft\Power Automate Desktop\RDP Automation Agents\*\PAD.RDP.AutomationAgent.exe,Microsoft.Flow.RPA.Desktop.UIAutomation.RDP.DVC.Plugin,PAD\UIA`
7074

7175
Ensure Citrix machines are restarted after applying the policy.
7276

7377
## More information
7478

7579
[Automate on virtual desktops](/power-automate/desktop-flows/virtual-desktops)
80+
81+
[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,18 +90,24 @@
9090
href: desktop-flows/ui-automation/desktop-application-crashes-ui-automation.md
9191
- name: Can't access the elements of a Java application
9292
href: desktop-flows/ui-automation/cannot-access-java-application-elements.md
93+
- name: Clicking elements doesn't work during runtime
94+
href: desktop-flows/ui-automation/ui-rdp-automation/no-clicks-on-runtime.md
9395
- name: Focus window action can't bring a window to focus
9496
href: desktop-flows/ui-automation/focus-window-action-not-working.md
9597
- name: Failed to get UI element
9698
href: desktop-flows/ui-automation/failed-get-ui-element.md
9799
- name: Failed to get element/window or Element/Window wasn't found errors
98100
href: desktop-flows/ui-automation/ui-automation-action-fails-errors.md
101+
- name: Interactions with RDP or Citrix applications take a long time and fail
102+
href: desktop-flows/ui-automation/ui-rdp-automation/interactions-with-rdp-citrix-takes-long-and-fails.md
99103
- name: SAP UI element click issue
100104
href: desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md
101105
- name: Set drop-down list value in window/on web page action fails
102106
href: desktop-flows/ui-automation/set-drop-down-list-value-fails.md
103107
- name: UI element highlighting or hovering issues in virtual desktops
104108
href: desktop-flows/ui-automation/ui-rdp-automation/rdp-no-highlight.md
109+
- name: '"The remote desktop was not found" error'
110+
href: desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md
105111
- name: UIPI issues with UI and web automation actions
106112
href: desktop-flows/ui-automation/uipi-issues.md
107113
- name: '"Could not read the application certificate" error when creating a connection'

0 commit comments

Comments
 (0)