Tool suggestions

Author: iopanag

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/collecting-debug-logs.md

@@ -10,24 +10,24 @@ ms.date: 03/28/2025
 
 # Collecting debug logs from agent for Virtual desktops
 
-This article will help you collect debug logs from remote Agent for Virtual Desktops. Most of the times this is not needed. However, when you have exhausted all troubleshooting methods for an RDP/Citrix issue, collecting debug logs from the remote machine might help with investigation.
+This article helps you collect debug logs from remote Agent for Virtual Desktops. Most of the times collecting these logs isn't needed. However, when you exhausted all troubleshooting methods for an RDP/Citrix issue, collecting debug logs from the remote machine might help with investigation.
 
 ## How to enable
 
-1. Login on the remote machine that is affected and set an environment variable either machine-wide or to specific affected user.
+1. Sign in on the remote machine that is affected and set an environment variable either machine-wide or to specific affected user.
 
     - Name: **PAD_DEBUG_RDP**
     - Value: **true**
 
 > [!NOTE]
 > You might need administrator rights on the remote machine to change environment variables.
 
-2. Log out of the remote affected session and log back in for the variable to take effect.
+2. Sign out of the remote affected session and log back in for the variable to take effect.
 3. Run the agent and try to perform the usual automation the user is trying to do.
 4. Afterwards check on the remote session Desktop folder for a folder named **PAD_RDP_DEBUG**
 5. Copy this folder to the desired machine.
 6. Check the logs for information you might not want to share.
-7. Remove the **PAD_DEBUG_RDP** environment variable from the remote machine to avoid to disable writing logs.
+7. Remove the **PAD_DEBUG_RDP** environment variable from the remote machine to avoid disabling writing logs.
 
 ## More information
 

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/configuring-timeouts.md

@@ -1,6 +1,6 @@
 ---
 title: Configuring timeouts for RDP/Citrix automations
-description: Guide on how configure certain timeout that affect RDP/Citrix automations on Power Automate.
+description: This article guides through the procedure needed to configure timeouts for RPD/Citrix automation.
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
@@ -10,20 +10,20 @@ ms.date: 03/28/2025
 
 # Configuring timeouts for RDP/Citrix automations
 
-There might be cases where interacting with RDP/Citrix applications might timeout and require additional time to work. These can be configured like the rest of Power Automate timeouts like in [Timeout 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.
+There might be cases where interacting with RDP/Citrix applications might timeout and require more time to work. These timeouts can be configured like the rest of Power Automate timeouts like in [Timeout 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.
 
 ## Issue: Something takes long time and fails afterwards
 
-The webpage/application may not repond fast to Power Automate requests. This is probably to application/webpage misbehaviour or bad connection to RDP/Citrix environment. Depending the application type you can extend the max wait time Power Automate will wait for response from the application:
+The webpage/application might not repond fast to Power Automate requests. This issue is probably due to application/webpage misbehavior or bad connection to RDP/Citrix environment. Depending on the application type you can extend the max wait time Power Automate waits for response from the application:
 
-- **Java.Bridge.Client.ReadWriteTimeout**: In case the target application is JAVA based, this will additionally increase time waiting for responses. In remote JAVA applications (RDP/Citrix), this is needed to be changed on the remote machine.
-- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**: In case web automation is used, this will increase the max time that will wait for webpage to respond. In remote webpages (RDP/Citrix), this is needed to be changed on the remote machine.
-- **RDP.Client.CallTimeOut**: When the application/webpage is on a remote machine, either RDP or Citrix. This will will additionaly increase the max time that will wait for the remote application/webpage to respond.
+- **Java.Bridge.Client.ReadWriteTimeout**: In case the target application is JAVA based, this timeout additionally increases time waiting for responses. In remote JAVA applications (RDP/Citrix), this timeout needs to be changed on the remote machine.
+- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**: In case web automation is used, this timeout increases the max time that waits for webpages to respond. In remote webpages (RDP/Citrix), this timeout 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 timeout additionally increases the max time that waits for the remote application/webpage to respond.
 
-If the problem is design oriented (e.g. failing to capture an Element from the designer), you will also need to configure the following too:
+If the problem is design oriented (for example, failing to capture an Element from the designer), you also need to configure the following too:
 
-- **AutomationServerEndpoint.DesignTime.CallTimeout**: This will increase the time the Power Automate Designer will wait for response.
+- **AutomationServerEndpoint.DesignTime.CallTimeout**: This increases the time the Power Automate Designer waits for response.
 
-If the problem is in runtime (when running the flow), you will also need to configure the following too:
+If the problem is in runtime (when running the flow), you also need to configure the following too:
 
-- **AutomationServerEndpoint.Runtime.CallTimeout**: This will increase the max time that runtime will wait for an action to be performed.
+- **AutomationServerEndpoint.Runtime.CallTimeout**: This increases the max time that runtime waits for an action to be performed.

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

@@ -9,40 +9,40 @@ ms.date: 03/28/2025
 ---
 # Error "The remote desktop was not found"
 
-This article helps you resolve an issue you may encounter when a flow fails with error 'The remote desktop was not found'.
+This article helps you resolve an issue you might encounter when a flow fails with error 'The remote desktop was not found'.
 
 ## Symptoms
 
-A flow using RDP/Citrix automation used to run successfully but it started failing with error 'The remote desktop was not found'. It might even never run successfully. This is more common in Citrix Virtual Apps.
+A flow using RDP/Citrix automation used to run successfully but it started failing with error 'The remote desktop was not found'. It might even never run successfully. This issue is more common in Citrix Virtual Apps.
 
 ## Cause 1
 
-The RDP Window/Citrix Desktop/Virtual App might have changed name since when the elements were captured and tracking them with the old name fails.
+The RDP Window/Citrix Desktop/Virtual App might changed name since when the elements were captured and tracking them with the old name fails.
 
 ### Resolution
 
 You can repair the selectors used to retract the RDP Window/Citrix Desktop/Virtual App like normal window selectors:
 
 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 its selector editor.
+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.
 
    :::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. Click on "Repair" button and capture the new Desktop/App. Check the suggested changes and accept them.
+3. Select on "Repair" button and capture the new Desktop/App. Check 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":::
 
-4. After Accepting the changes, Click on the "Test" to test the new selector.
-5. [Optionally if needed] You can use the "New" Button to add additional fallback selectors for the desktop.
+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.
 
 ## 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 listes.
+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.
 
 ### 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 its selector editor.
+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.
 
    :::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.":::
 

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

@@ -1,30 +1,30 @@
 ---
-title: Elements are highlighted but on runtime clicks are not happening on Citrix Virtual apps
-description: Solves an issue that occurs when hovering over elements in Citrix Virtual apps works but on runtime clicks do not work
+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
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
 ms.custom: sap:Desktop flows\UI or browser automation
 ms.date: 03/28/2025
 ---
-# Elements are highlighted but on runtime clicks are not happening on Citrix Virtual apps
+# Elements are highlighted but on runtime clicks aren't happening on Citrix Virtual apps
 
-This article helps you resolve an issue you may encounter when trying to click an element in Citrix Virtual apps.
+This article helps you resolve an issue you might encounter when trying to click an element in Citrix Virtual apps.
 
 ## Symptoms
 
-When you hover the mouse cursor over a UI or web element of an application or webpage inside a Citrix virtual app with [UI element picker](/power-automate/desktop-flows/ui-elements#ui-elements-types) the elements are highlighted and captured, however when used in an action, the interaction is not happening and no error is shown. Test selector works fine.
+When you hover the mouse cursor over a UI or web element of an application or webpage inside a Citrix virtual app with [UI element picker](/power-automate/desktop-flows/ui-elements#ui-elements-types) the elements are highlighted and captured. However when used in an action (like 'Click Element in Window'), the interaction isn't happening and no error is shown. Test selector works fine.
 
 ## Cause
 
-The Citrix Workspace HI DPI settings are interfering with PAD interactions. Mostly affected setups with multiple monitors.
+The Citrix Workspace HIDPI settings are interfering with PAD interactions. Mostly affected setups with multiple monitors.
 
 ## Resolution
 
 1. Disable Citrix Workspace HIDPI option. From the tray icon right click on the Citrix Workspace icon.
-2. Click on 'Advanced Preferences'.
+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)
+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)

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/recorder-not-recording-keystrokes.md

@@ -11,11 +11,11 @@ ms.date: 03/28/2025
 
 ## Symptoms
 
-When using the recorder on an RDP window, the keystores are not recorded but other interactions (like clicks) are recorded fine.
+When you use the recorder on an RDP window, the keystores aren't recorded but other interactions (like clicks) are recorded fine.
 
 ## Causes
 
-The RDP window is in Maximized state. This is a limitation of the RDP clients that intercept keystrokes and interferes with the recorder when the window is maximized.
+The RDP window is in Maximized state. This issue is a limitation of the RDP clients that intercept keystrokes and interferes with the recorder when the window is maximized.
 
 ## Resolution
 

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/troubleshooting-with-the-troubleshooter.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting RDP or Citrix automation issues with the Troubleshooter
-description: Guide on how use the Power Automate troubleshooter to diagnose RDP/Citrix automation issues.
+description: Guide on how to use the Power Automate troubleshooter to diagnose RDP/Citrix automation issues.
 ms.reviewer: amitrou
 ms.author: iopanag
 author: iopanag
@@ -10,11 +10,11 @@ ms.date: 03/28/2025
 
 # Troubleshooting RDP or Citrix automation issues with the Troubleshooter
 
-This article will help you use the Power Automate troubleshooter to diagnose and potentialy solve issues related to RDP or Citrix automation. When faced with such issues, the troubleshooter should be the first course of actions for diagnosing the problem.
+This article helps you use the Power Automate troubleshooter to diagnose and potentially solve issues related to RDP or Citrix automation. When faced with such issues, the troubleshooter should be the first course of actions for diagnosing the problem.
 
 ## How to diagnose issues with the troubleshooter
 
-1. Make sure the problematic remote RDP/Citrix session/app is up. The troubleshooter will attempt to connect with it to check for issues.
+1. Make sure the problematic remote RDP/Citrix session/app is up. The troubleshooter attempts to connect with it to check for issues.
 2. Launch the troubleshooter from the Power Automate menu, `Help -> Troubleshooter`
 
    :::image type="content" source="media/troubleshooting-with-the-troubleshooter/launch-troubleshooter-menu.png" alt-text="Screenshot of the Power Automate designer help menu with the Troubleshooter option highlighted.":::