Skip to content

Commit 09b8b47

Browse files
authored
Merge pull request #4905 from johndund/main
AB#181170: Update troubleshoot-errors-running-attended-or-unattended-desktop-flo…
2 parents 15a7fc5 + b7ebdee commit 09b8b47

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

support/power-platform/power-automate/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Error code occurs when running an attended or unattended desktop flow
33
description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
4-
ms.reviewer: cefriant, kenseongtan, guco
5-
ms.date: 08/25/2023
4+
ms.reviewer: cefriant, kenseongtan, guco, johndund
5+
ms.date: 09/11/2023
66
ms.subservice: power-automate-desktop-flows
77
---
88
# Error code occurs when running an attended or unattended desktop flow
@@ -51,3 +51,4 @@ _Original KB number:_   4555406
5151
|WcfServerCrash|500|Attended</br>Unattended|This error code occurs when the machine encounters an unexpected error while answering the cloud orchestrator. </br>- Verify that the machine has sufficient compute and memory resources while running the automation.</br>- Ensure that the network connection is stable during the automation. </br>- Ensure that you have the latest version of Power Automate for desktop installed.|
5252
|RdpPermissionNotGranted|400|Unattended|This error occurs when the user specified in the connection doesn't have permissions to create remote desktop sessions on the machine. </br>- Verify that the user in question is included in either the Administrators or Remote Desktop Users group on the machine.|
5353
|XrmMachineGroupNotFound|404|Attended</br>Unattended|This error occurs when the machine group has been deleted. Please re-create the group and update the connection.|
54+
|SessionCreationInvalidCredentials|400|Unattended|This error occurs when the unattended session couldn't be created with the provided credentials. This issue might occur due to an incorrectly formatted username. For Azure Active Directory (AAD)-joined machines, ensure the username is in the `[email protected]` format. For domain-joined machines, the username should be in the `domain\user` format.|

0 commit comments

Comments
 (0)