You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,47 +5,49 @@ ms.reviewer: amitrou
5
5
ms.author: iopanag
6
6
author: iopanag
7
7
ms.custom: sap:Desktop flows\UI or browser automation
8
-
ms.date: 04/15/2025
8
+
ms.date: 04/16/2025
9
9
---
10
10
# A desktop flow fails with the "The remote desktop wasn't found" error
11
11
12
-
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.
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
13
14
14
## Symptoms
15
15
16
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
17
18
18
> The remote desktop wasn't found.
19
19
20
-
In some cases, the flow might never run successfully. This issue is more commonly observed in Citrix Virtual Apps.
20
+
This issue is more common in Citrix Virtual Apps.
21
21
22
22
## Cause 1
23
23
24
-
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.
24
+
The names 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.
25
25
26
26
### Resolution
27
27
28
-
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:
28
+
To solve this issue,
29
29
30
30
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
31
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
32
33
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
34
35
-
3. Select the **Repair** button and capture the new desktop or app. Review the suggested changes and accept them.
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
36
37
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
38
39
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
40
41
-
5. (Optionally) Use the **New** button to add more fallback selectors for the desktop, if necessary.
41
+
5. (Optionally) Use the **New** button to add more fallback selectors for the desktop.
42
42
43
43
## Cause 2
44
44
45
-
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.
45
+
When you use Citrix Virtual Apps with certain applications, especially when interacting with combo box lists, an incorrect target desktop selector may be created using an ordinal value (for example, **eq**) instead of a more robust selection method.
46
46
47
47
### Resolution
48
48
49
+
To solve this issue,
50
+
49
51
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
50
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.
51
53
@@ -56,3 +58,5 @@ When you use Citrix Virtual Apps with certain applications, an incorrect target
56
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.":::
57
59
58
60
4. Select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).
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/16/2025
9
+
---
10
+
# Interactions with RDP or Citrix applications take a long time and fail
11
+
12
+
This article provides guidance on resolving an issue where operation takes a long time and fails afterwards by adjusting certain time-out configurations.
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 being 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 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.
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/no-clicks-on-runtime.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ ms.reviewer: amitrou
5
5
ms.author: iopanag
6
6
author: iopanag
7
7
ms.custom: sap:Desktop flows\UI or browser automation
8
-
ms.date: 04/15/2025
8
+
ms.date: 04/16/2025
9
9
---
10
10
# Elements are highlighted in Citrix Virtual Apps but runtime clicks on the elements don't work
11
11
12
-
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.
12
+
This article provides steps to resolve an issue where UI element interactions don't occur when running actions in Citrix Virtual Apps, despite the UI elements being properly highlighted and captured.
13
13
14
14
## Symptoms
15
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.
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
17
18
18
## Cause
19
19
@@ -34,3 +34,5 @@ To solve this issue, follow these steps:
34
34
1. Restart the Citrix Desktops or Virtual Apps.
35
35
36
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).
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/something-takes-long-and-fails.md
0 commit comments