From 905c0025e09c53b87b45d8c283cf07c517db89c2 Mon Sep 17 00:00:00 2001 From: lulubran <129538431+lulubran@users.noreply.github.com> Date: Tue, 24 Sep 2024 14:54:46 +0200 Subject: [PATCH 1/2] Add new unattended error codes in troubleshoot-desktop-flow-run-queue-errors.md Add UnattendedUserSessionDisconnected and UnattendedUserSessionLocked --- ...troubleshoot-desktop-flow-run-queue-errors.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md b/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md index 3b5744e0e3..e5191b6c0f 100644 --- a/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md +++ b/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md @@ -43,17 +43,21 @@ This error occurs when you try to run an unattended desktop flow on a target mac To resolve the issue, sign out of the session (a locked session will lead to this error), and confirm that you aren't signed in with the same user on the machine. -## NoUnlockedActiveSessionForAttended +## UnattendedUserSessionDisconnected -This error usually occurs when you try to run an attended desktop flow on a target machine that is locked or has no user signed in. You can also get this error when the Windows user you're currently signed in on the target machine doesn't match the user you entered in your connection. Attended desktop flows can only execute if the machine is unlocked on a session where the current user matches the one in the desktop flow connection. +This error occurs when you try to run an unattended desktop flow on a target machine where there is a disconnected session for the user used in the desktop flow connection. #### Resolution -To resolve the issue: +To resolve the issue, sign out of the disconnected session, and confirm that you aren't signed in with the same user on the machine. -- Check the credentials used in your connection and make sure they're the ones used in the unlocked session. You can verify your identity by typing `whoami` in any command prompt. -- Verify that you're targeting the right machine. To do so, open the machine runtime application and select **View machine in portal** to verify that it brings you to the machine you're targeting in your run. -- Verify that the account that runs the Power Automate service (UIFlowService) has Remote Desktop permissions on the machine. By default, the Power Automate service runs as `NT SERVICE\UIFlowService`. If you didn't change this, verify that `NT SERVICE\UIFlowService` is in the **Remote Desktop Users** group. To do so, go to **Start** > **Run**, type *usrmgr.msc*, select **Groups**, double-click the **Remote Desktop Users** group and verify the account is included. If it's not included, include it (this requires administrator permissions) and restart the machine. +## UnattendedUserSessionLocked + +This error occurs when you try to run an unattended desktop flow on a target machine where there is a locked session for the user used in the desktop flow connection. + +#### Resolution + +To resolve the issue, sign out of the locked session, and confirm that you aren't signed in with the same user on the machine. ## AttendedUserSessionNotActive From 66b0c3bb6ae12ac65baf0b63b40be63a85ef5109 Mon Sep 17 00:00:00 2001 From: lulubran <129538431+lulubran@users.noreply.github.com> Date: Tue, 24 Sep 2024 15:06:15 +0200 Subject: [PATCH 2/2] Revert unexpected change --- .../troubleshoot-desktop-flow-run-queue-errors.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md b/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md index e5191b6c0f..688738485c 100644 --- a/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md +++ b/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md @@ -59,6 +59,18 @@ This error occurs when you try to run an unattended desktop flow on a target mac To resolve the issue, sign out of the locked session, and confirm that you aren't signed in with the same user on the machine. +## NoUnlockedActiveSessionForAttended + +This error usually occurs when you try to run an attended desktop flow on a target machine that is locked or has no user signed in. You can also get this error when the Windows user you're currently signed in on the target machine doesn't match the user you entered in your connection. Attended desktop flows can only execute if the machine is unlocked on a session where the current user matches the one in the desktop flow connection. + +#### Resolution + +To resolve the issue: + +- Check the credentials used in your connection and make sure they're the ones used in the unlocked session. You can verify your identity by typing `whoami` in any command prompt. +- Verify that you're targeting the right machine. To do so, open the machine runtime application and select **View machine in portal** to verify that it brings you to the machine you're targeting in your run. +- Verify that the account that runs the Power Automate service (UIFlowService) has Remote Desktop permissions on the machine. By default, the Power Automate service runs as `NT SERVICE\UIFlowService`. If you didn't change this, verify that `NT SERVICE\UIFlowService` is in the **Remote Desktop Users** group. To do so, go to **Start** > **Run**, type *usrmgr.msc*, select **Groups**, double-click the **Remote Desktop Users** group and verify the account is included. If it's not included, include it (this requires administrator permissions) and restart the machine. + ## AttendedUserSessionNotActive This error occurs when the user specified in the connection is signed in to the target machine but the target session is either in a locked or disconnected state.