Skip to content

Commit 36626dc

Browse files
authored
minor changes
1 parent 42fe842 commit 36626dc

5 files changed

Lines changed: 73 additions & 63 deletions

File tree

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

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,47 +5,49 @@ ms.reviewer: amitrou
55
ms.author: iopanag
66
author: iopanag
77
ms.custom: sap:Desktop flows\UI or browser automation
8-
ms.date: 04/15/2025
8+
ms.date: 04/16/2025
99
---
1010
# A desktop flow fails with the "The remote desktop wasn't found" error
1111

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

1414
## Symptoms
1515

1616
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:
1717

1818
> The remote desktop wasn't found.
1919
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.
2121

2222
## Cause 1
2323

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.
2525

2626
### Resolution
2727

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,
2929

3030
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
3131
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.
3232

3333
:::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.":::
3434

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).
3636

3737
:::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.":::
3838

3939
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).
4040

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.
4242

4343
## Cause 2
4444

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.
4646

4747
### Resolution
4848

49+
To solve this issue,
50+
4951
1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
5052
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.
5153

@@ -56,3 +58,5 @@ When you use Citrix Virtual Apps with certain applications, an incorrect target
5658
:::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.":::
5759

5860
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/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.
52+
53+
[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ ms.reviewer: amitrou
55
ms.author: iopanag
66
author: iopanag
77
ms.custom: sap:Desktop flows\UI or browser automation
8-
ms.date: 04/15/2025
8+
ms.date: 04/16/2025
99
---
1010
# Elements are highlighted in Citrix Virtual Apps but runtime clicks on the elements don't work
1111

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

1414
## Symptoms
1515

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.
1717

1818
## Cause
1919

@@ -34,3 +34,5 @@ To solve this issue, follow these steps:
3434
1. Restart the Citrix Desktops or Virtual Apps.
3535

3636
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: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.reviewer: amitrou
55
ms.author: nimoutzo
66
author: NikosMoutzourakis
77
ms.custom: sap:Desktop flows\UI or browser automation
8-
ms.date: 04/15/2025
8+
ms.date: 04/16/2025
99
---
1010
# UI element isn't highlighted or an error occurs when hovering over a UI or web element
1111

@@ -77,3 +77,5 @@ The communication with the remote agent components doesn't work.
7777
## More information
7878

7979
[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/desktop-flows/ui-automation/ui-rdp-automation/something-takes-long-and-fails.md

Lines changed: 0 additions & 51 deletions
This file was deleted.

0 commit comments

Comments
 (0)