Skip to content

Commit 13edf25

Browse files
authored
Updates
1 parent a826596 commit 13edf25

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

support/power-platform/power-automate/desktop-flows/browser-automation/js-not-executed.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Run JavaScript function on Web Page Action Fails to Execute
2+
title: Run JavaScript Function on Web Page Action Fails to Execute
33
description: Solves an issue where the Run JavaScript function on web page action isn't executed and returns no error.
44
ms.custom: sap:Desktop flows\UI or browser automation
55
ms.reviewer: amitrou

support/power-platform/power-automate/desktop-flows/ui-automation/uipi-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article provides guidance for resolving issues caused by User Interface Pri
1515

1616
Actions performing UI or browser automation might fail with an error message similar to the following one:
1717

18-
> System.Exception: Some simulated input commands were not sent successfully. The most common reason for this happening are the security features of Windows including User Interface Privacy Isolation (UIPI). Your application can only send commands to applications of the same or lower elevation. Similarly certain commands are restricted to Accessibility/UIAutomation applications. Refer to the project home page and the code samples for more information
18+
> System.Exception: Some simulated input commands were not sent successfully. The most common reason for this happening are the security features of Windows including User Interface Privacy Isolation (UIPI). Your application can only send commands to applications of the same or lower elevation. Similarly certain commands are restricted to Accessibility/UIAutomation applications. Refer to the project home page and the code samples for more information.
1919
2020
## Cause 1: The desktop is locked during execution
2121

0 commit comments

Comments
 (0)