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/element-picker-cant-see-elements.md
+15-21Lines changed: 15 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
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.
2
+
title: Troubleshoot UI Automation and Element Detection in Power Automate for Desktop
3
+
description: Troubleshoot UI automation issues in Power Automate for desktop. Learn how to fix problems with the element picker or recorder not detecting UI elements.
4
4
ms.date: 12/02/2025
5
5
ms.custom: sap:Desktop flows\UI or browser automation
6
6
ms.reviewer: iomimtso, nimoutzo, v-shaywood
@@ -15,35 +15,29 @@ This article provides troubleshooting guidance for issues where Power Automate f
15
15
16
16
When you try to use UI automation in Power Automate for desktop, you might experience the following issues:
17
17
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.
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
20
21
-
## Causes
21
+
## Cause 1: Interfering background processes
22
22
23
-
UI automation issues in Power Automate for desktop can occur due to the following reasons:
23
+
Some background processes interfere with UI automation functionality in Power Automate for desktop. Specifically, the **Microsoft Accessory Center** or **DesktopBridge** processes prevent UI automation from working correctly.
24
24
25
-
### Cause 1: Interfering background processes
25
+
### Solution: Terminate interfering processes
26
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.
27
+
To resolve this issue, terminate the interfering processes and disable them from running in the future.
28
28
29
-
###Cause 2: Incompatible UI frameworks
29
+
## Cause 2: Incompatible UI frameworks
30
30
31
-
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.
31
+
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 makes certain elements invisible to the element picker.
32
32
33
33
> [!IMPORTANT]
34
-
> For coordinate-based solutions (Solutions [4](#solution-4-use-the-recorder-with-coordinates) and [5](#solution-5-use-move-mouse-and-send-mouse-click-actions)) to work reliably:
34
+
> For coordinate-based solutions (Solutions [3](#solution-3-use-the-recorder-with-coordinates) and [4](#solution-4-use-move-mouse-and-send-mouse-click-actions)) to work reliably:
35
35
>
36
36
> - The screen configuration (resolution, DPI settings, scaling) must remain static at runtime and match the configuration used during development.
37
37
> - Changes to the application's user interface structure might affect the effectiveness of these workarounds.
38
38
> - 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.
45
39
46
-
## Solution 2: Use Move mouse to image action
40
+
###Solution 1: Use Move mouse to image action
47
41
48
42
1. Add a **Move mouse to image** action to your flow.
49
43
1. Capture an image of the UI element you want to interact with.
@@ -52,7 +46,7 @@ To resolve this issue, terminate the interfering processes and prevent them from
52
46
53
47
This action moves the mouse to the first occurrence of the specified image and sends a left click.
54
48
55
-
## Solution 3: Use Move mouse to text on screen (OCR) action
49
+
## Solution 2: Use Move mouse to text on screen (OCR) action
56
50
57
51
1. Add a **Move mouse to text on screen (OCR)** action to your flow.
58
52
1. Specify the text that appears on or near the UI element you want to interact with.
@@ -61,7 +55,7 @@ This action moves the mouse to the first occurrence of the specified image and s
61
55
62
56
This action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
63
57
64
-
## Solution 4: Use the recorder with coordinates
58
+
## Solution 3: Use the recorder with coordinates
65
59
66
60
1. Open Power Automate for desktop and create a new flow.
67
61
1. Select **Recorder** from the toolbar.
@@ -70,7 +64,7 @@ This action uses Optical Character Recognition (OCR) to locate text on the scree
70
64
71
65
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.
72
66
73
-
## Solution 5: Use Move mouse and Send mouse click actions
67
+
## Solution 4: Use Move mouse and Send mouse click actions
74
68
75
69
1. Add a **Move mouse** action to your flow.
76
70
1. Configure the action to move the mouse to the specific coordinates of the target element.
0 commit comments