UI automation actions fail after Block Input action

Author: iomimtso

support/power-platform/power-automate/desktop-flows/ui-automation/block-input-action-issues.md

@@ -0,0 +1,78 @@
+---
+title: UI automation actions fail after Block Input action
+description: Resolves an issue where UI or web automation actions that involve mouse or keyboard input don't work as expected after a Block Input action in Power Automate for desktop.
+ms.reviewer: nimoutzo, jspantouris
+ms.author: iomimtso
+ms.date: 11/21/2025
+ms.custom: sap:Desktop flows\UI or browser automation
+---
+# UI automation actions fail after Block Input action
+
+This article provides resolutions for an issue where 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.
+
+## Symptoms
+
+When you run a desktop flow that includes a Block Input action with the **Block It** parameter set to **True**, UI or web automation actions that follow might not work as expected. The flow continues to the next actions without showing any errors, but the mouse or keyboard interactions aren't executed.
+
+The following actions might not work correctly after a Block Input action:
+
+- Populate text field in window
+- Press button in window
+- Select radio button in window
+- Set checkbox state in window
+- Set drop-down list value in window
+- Click UI element in window
+- Select tab in window
+- Hover mouse over UI element in window
+- Click link on web page (when the **Send Physical Click** option is enabled)
+- Populate text field on web page (when the **Populate text using physical keystrokes** option is enabled)
+- Send keys
+
+## Cause
+
+The Block Input action requires elevated rights to run because of its critical functionality. When Block Input is active with **Block It** set to **True**, it can interfere with subsequent UI or web automation actions that require physical mouse or keyboard input.
+
+> [!NOTE]
+> The Block Input action is functional only when you run a desktop flow through the console or debug it through the designer, and only if Power Automate for desktop runs with elevated rights. For more information, see [Run Power Automate with elevated rights](/power-automate/desktop-flows/how-to/run-power-automate-elevated-rights).
+
+## Resolution
+
+Use one of the following methods to resolve this issue.
+
+### Method 1: Avoid using the Block Input action
+
+If possible, design your flow without the Block Input action to prevent this issue.
+
+### Method 2: Use alternative mouse and keyboard actions
+
+If you need to use Block Input and perform mouse actions, use 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).
+
+#### Option A: Use Move mouse and Send mouse click actions
+
+1. Use the **Move mouse** action to move the mouse pointer to a specific position.
+2. Use the **Send mouse click** action to perform the click.
+
+The **Move mouse** action requires you to specify coordinates. You can use the **Relative to** parameter to specify whether the new mouse position is relative to:
+
+- **Current Mouse Position**
+- **Active Window** (the foremost window)
+- **Screen** (relative to the upper-left corner of the screen)
+
+#### Option B: Use Move mouse to Image action
+
+Use the **Move mouse to Image** action with the **Send 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.
+
+#### Option C: Use Move mouse to Text on Screen (OCR) action
+
+Use the **Move mouse to Text on Screen (OCR)** action with 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.
+
+### Method 3: Temporarily disable Block Input
+
+If you need to use Block Input but also need to perform actions that require physical input, use this approach:
+
+1. Use the **Block Input** action with **Block It** set to **True** when you need input blocked.
+2. Before executing a UI or web automation action that requires mouse or keyboard input, add a **Block Input** action with **Block It** set to **False**.
+3. Execute the UI or web automation action.
+4. If you still need to block input after the action, add another **Block Input** action with **Block It** set to **True**.
+
+This method allows you to temporarily enable physical input for specific actions while maintaining input blocking for the rest of the flow.