|
| 1 | +--- |
| 2 | +title: Troubleshoot UI Automation Action Failures After a Block Input Action |
| 3 | +description: Resolves an issue in which UI or web automation actions fail after a Block Input action in Power Automate for desktop. |
| 4 | +ms.reviewer: iomimtso, nimoutzo, jspantouris, v-shaywood |
| 5 | +ms.date: 11/21/2025 |
| 6 | +ms.custom: sap:Desktop flows\UI or browser automation |
| 7 | +--- |
| 8 | +# UI automation actions fail after Block Input action |
| 9 | + |
| 10 | +This article provides solutions for an issue in which UI or web automation actions that involve mouse or keyboard input don't work as expected after you use a **Block Input** action in Power Automate for desktop. |
| 11 | + |
| 12 | +## Symptoms |
| 13 | + |
| 14 | +When you run a desktop flow that includes a [Block Input](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#blockinput) action by having the **Block It** parameter set to **True**, subsequent UI or web automation actions might not work as expected. The flow continues to the next actions without showing any errors, but the mouse or keyboard interactions aren't run. |
| 15 | + |
| 16 | +The following actions might not work correctly after a **Block Input** action: |
| 17 | + |
| 18 | +- Populate text field in window |
| 19 | +- Press button in window |
| 20 | +- Select radio button in window |
| 21 | +- Set checkbox state in window |
| 22 | +- Set drop-down list value in window |
| 23 | +- Click UI element in window |
| 24 | +- Select tab in window |
| 25 | +- Hover mouse over UI element in window |
| 26 | +- Click link on web page (if the **Send Physical Click** option is enabled) |
| 27 | +- Populate text field on web page (if the **Populate text using physical keystrokes** option is enabled) |
| 28 | +- Send keys |
| 29 | + |
| 30 | +## Cause |
| 31 | + |
| 32 | +The **Block Input** action requires elevated rights to run because of its critical functionality. If **Block Input** is active by having **Block It** set to **True**, the action can interfere with subsequent UI or web automation actions that require physical mouse or keyboard input. |
| 33 | + |
| 34 | +> [!NOTE] |
| 35 | +> The **Block Input** action works only when you: |
| 36 | +> |
| 37 | +> - Run a desktop flow through the console or debug it through the designer. |
| 38 | +> - Run Power Automate for desktop runs by having elevated rights. |
| 39 | +> |
| 40 | +> For more information, see [Run Power Automate with elevated rights](/power-automate/desktop-flows/how-to/run-power-automate-elevated-rights). |
| 41 | +
|
| 42 | +## Solution 1: Don't use the Block Input action |
| 43 | + |
| 44 | +To prevent this issue, design your flow without the **Block Input** action, if possible. |
| 45 | + |
| 46 | +## Solution 2: Use alternative mouse and keyboard actions |
| 47 | + |
| 48 | +If you have to use **Block Input** and perform mouse actions, use one of the following actions from the _Mouse and keyboard_ category instead of UI automation actions. For more information, see [Mouse and keyboard actions reference](/power-automate/desktop-flows/actions-reference/mouseandkeyboard). |
| 49 | + |
| 50 | +### Alternative A: Use Move mouse and Send mouse click actions |
| 51 | + |
| 52 | +1. Use the [Move mouse](/power-automate/desktop-flows/actions-reference/mouseandkeyboard?source=recommendations#movemouse) action to move the mouse pointer to a specific position. |
| 53 | +1. Use the [Send mouse click](/power-automate/desktop-flows/actions-reference/mouseandkeyboard?source=recommendations#sendmouseclick) action to perform the click. |
| 54 | + |
| 55 | +The **Move mouse** action requires you to specify coordinates. Use the **Relative to** parameter to specify whether the new mouse position is relative to: |
| 56 | + |
| 57 | +- **Current Mouse Position** |
| 58 | +- **Active Window** (the foremost window) |
| 59 | +- **Screen** (relative to the upper-left corner of the screen) |
| 60 | + |
| 61 | +### Alternative B: Use Move mouse to Image action |
| 62 | + |
| 63 | +Use the [Move mouse to Image](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#movemousetoimagebase) action by having the **Send a click after moving mouse** option enabled. This action moves the mouse to the position of a specified image on the screen, and then sends a click. |
| 64 | + |
| 65 | +### Alternative C: Use Move mouse to Text on Screen (OCR) action |
| 66 | + |
| 67 | +Use the [Move mouse to Text on Screen (OCR)](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#movemousetotextonscreenwithocraction) action by having the **Send a click after moving mouse** option enabled. This action uses optical character recognition (OCR) to locate text on the screen, moves the mouse to that position, and then sends a click. |
| 68 | + |
| 69 | +### Solution 3: Temporarily disable Block Input |
| 70 | + |
| 71 | +If you have to use **Block Input** but also have to perform actions that require physical input, use the following method: |
| 72 | + |
| 73 | +1. If you need input blocked, use the **Block Input** action by having **Block It** set to **True**. |
| 74 | +1. Before you run a UI or web automation action that requires mouse or keyboard input, add a **Block Input** action that has **Block It** set to **False**. |
| 75 | +1. Run the UI or web automation action. |
| 76 | +1. If you still have to block input after the action runs, add another **Block Input** action that has **Block It** set to **True**. |
| 77 | + |
| 78 | +This method lets you temporarily enable physical input for specific actions and also maintains input blocking for the rest of the flow. |
0 commit comments