Skip to content

Commit 1ceaa5d

Browse files
committed
Update article with new cause
1 parent fd61ea3 commit 1ceaa5d

File tree

1 file changed

+29
-11
lines changed

1 file changed

+29
-11
lines changed

support/power-platform/power-automate/desktop-flows/ui-automation/element-picker-cant-see-elements.md

Lines changed: 29 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,32 @@
11
---
2-
title: Troubleshoot UI Element Visibility Issues in Power Automate for Desktop
3-
description: Troubleshoot Power Automate for desktop when it can't interact with specific UI elements. Explore solutions like OCR, image actions, and more.
4-
ms.date: 11/05/2025
2+
title: UI automation fails and element picker or recorder can't see UI elements
3+
description: Resolves issues where UI automation doesn't work and no UI elements are shown in the element picker or recorder when Microsoft Accessory Center or DesktopBridge processes are running, or when applications use incompatible UI frameworks.
4+
ms.date: 12/02/2025
55
ms.custom: sap:Desktop flows\UI or browser automation
66
ms.reviewer: iomimtso, nimoutzo, v-shaywood
7+
ms.author: iomimtso
78
---
89

9-
# UI element picker or recorder can't view UI elements in desktop applications
10+
# UI automation fails and element picker or recorder can't see UI elements
1011

11-
This article provides troubleshooting guidance for an issue where Power Automate for desktop can't view or interact with specific UI elements in a desktop application.
12+
This article provides troubleshooting guidance for issues where Power Automate for desktop can't view or interact with specific UI elements in a desktop application.
1213

1314
## Symptoms
1415

15-
When using Power Automate for desktop, the element picker tool can't detect or "see" certain UI elements within desktop applications. This issue prevents you from selecting elements for automation tasks.
16+
When you try to use UI automation in Power Automate for desktop, you might experience the following issues:
1617

17-
## Cause
18+
- **During design time**: The element picker or recorder doesn't show any UI elements when you try to capture elements for automation.
19+
- **During runtime**: UI automation actions fail to execute correctly in both attended and unattended desktop flow runs.
20+
21+
## Causes
22+
23+
UI automation issues in Power Automate for desktop can occur due to the following reasons:
24+
25+
### Cause 1: Interfering background processes
26+
27+
Certain background processes interfere with UI automation functionality in Power Automate for desktop. Specifically, the **Microsoft Accessory Center** or **DesktopBridge** processes can prevent UI automation from working correctly.
28+
29+
### Cause 2: Incompatible UI frameworks
1830

1931
Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with the standard accessibility APIs that Power Automate for desktop relies on. This incompatibility can make certain elements invisible to the element picker.
2032

@@ -24,8 +36,14 @@ Some desktop applications use custom UI frameworks or rendering methods that are
2436
> - The screen configuration (resolution, DPI settings, scaling) must remain static at runtime and match the configuration used during development.
2537
> - Changes to the application's user interface structure might affect the effectiveness of these workarounds.
2638
> - Test your flows thoroughly when deploying to different machines or environments.
39+
>
40+
> Solutions [2](#solution-2-use-move-mouse-to-image-action) through [5](#solution-5-use-move-mouse-and-send-mouse-click-actions) are workarounds for applications with incompatible UI frameworks (see [Cause 2](#cause-2-incompatible-ui-frameworks)). If your issue is caused by interfering processes, try [Solution 1](#solution-1-terminate-interfering-processes) first.
41+
42+
## Solution 1: Terminate interfering processes
43+
44+
To resolve this issue, terminate the interfering processes and prevent them from running in the future.
2745

28-
## Solution 1: Use Move mouse to image action
46+
## Solution 2: Use Move mouse to image action
2947

3048
1. Add a **Move mouse to image** action to your flow.
3149
1. Capture an image of the UI element you want to interact with.
@@ -34,7 +52,7 @@ Some desktop applications use custom UI frameworks or rendering methods that are
3452

3553
This action moves the mouse to the first occurrence of the specified image and sends a left click.
3654

37-
## Solution 2: Use Move mouse to text on screen (OCR) action
55+
## Solution 3: Use Move mouse to text on screen (OCR) action
3856

3957
1. Add a **Move mouse to text on screen (OCR)** action to your flow.
4058
1. Specify the text that appears on or near the UI element you want to interact with.
@@ -43,7 +61,7 @@ This action moves the mouse to the first occurrence of the specified image and s
4361

4462
This action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
4563

46-
## Solution 3: Use the recorder with coordinates
64+
## Solution 4: Use the recorder with coordinates
4765

4866
1. Open Power Automate for desktop and create a new flow.
4967
1. Select **Recorder** from the toolbar.
@@ -52,7 +70,7 @@ This action uses Optical Character Recognition (OCR) to locate text on the scree
5270

5371
The recorder creates a **Click UI element in window** action with coordinate-based input parameters populated by using the respective values from your click action.
5472

55-
## Solution 4: Use Move mouse and Send mouse click actions
73+
## Solution 5: Use Move mouse and Send mouse click actions
5674

5775
1. Add a **Move mouse** action to your flow.
5876
1. Configure the action to move the mouse to the specific coordinates of the target element.

0 commit comments

Comments
 (0)