|
2 | 2 | title: Error code occurs when running an attended or unattended desktop flow |
3 | 3 | description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows. |
4 | 4 | ms.reviewer: cefriant, kenseongtan, guco, johndund |
5 | | -ms.date: 12/27/2024 |
| 5 | +ms.date: 01/15/2024 |
6 | 6 | ms.custom: sap:Desktop flows\Unattended flow runtime errors |
7 | 7 | --- |
8 | 8 | # Error code occurs when running an attended or unattended desktop flow |
@@ -58,8 +58,10 @@ _Original KB number:_ 4555406 |
58 | 58 | |DesktopFlowMalformedMachineResponse|500|Attended</br>Unattended|This error code occurs when the target machine provides an unexpected response to 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.| |
59 | 59 | |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.| |
60 | 60 | |DataverseTimeout|504|Attended</br>Unattended|A desktop flow has been triggered and then failed due to a time-out of a Dataverse call. Take the following steps to solve this issue:</br>1. Scale up your Dataverse instance. Contact your administrator for assistance with this step.</br>2. Identify the heavily used Dataverse instance. The Dataverse call might be affected by other users using the same Dataverse instance in parallel.</br>3. Contact Microsoft Support for further assistance if this issue persists in your environment.| |
61 | | -|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.| |
| 61 | +|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.</br>- Verify that there are no deny policies interfering. Go to start > **Run**, and type _secpol.msc_ to open the Local Security Policy console. Then, navigate to **Security Settings** > **Local Policies** > **User Rights Assignment**. Ensure that both the **Deny log on locally** and **Deny log on through Remote Desktop Services** settings don't include the account running the Power Automate service (UIFlowService). To find out which account this is, see the [troubleshoot experience](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account) in the runtime application.| |
62 | 62 | |XrmMachineGroupNotFound|404|Attended</br>Unattended|This error occurs when the machine group has been deleted. Re-create the group and update the connection.| |
63 | 63 | |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 Microsoft Entra joined machines, ensure the username is in the `[email protected]` format. For domain-joined machines, the username should be in the `domain\user` format. | |
64 | 64 | |UIFlowServiceNoRdpPermissions|400|Unattended|This error occurs when the Power Automate service ([UIFlowService](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account)) running on your computer can't list the Windows sessions on the machine. </br> Add the user account that the service runs as (usually **NT SERVICE\UIFlowService**) to the "Remote Desktop Users" group on your machine.| |
65 | | -|UnallowedTenantForConnectWithSignIn|403|Attended |This error occurs when using a [connect with sign-in](/power-automate/desktop-flows/desktop-flow-connections#connect-with-sign-in-for-attended-runs) connection on an Active Directory (AD) domain-joined machine without having added your tenant to the allowlist. </br> For more information, see ["UnallowedTenantForConnectWithSignIn" error in a Power Automate desktop flow](troubleshoot-unallowed-tenant-for-connect-with-sign-in.md).| |
| 65 | +|AccountLockedOut|400|Unattended|This error occurs when an internal system policy has prevented an account from creating a session on the machine because of too many sign-in attempts or password change attempts for the account. It's related to an on-premises configuration, not Power Automate licenses. Check that password rotation policies don't interfere with your scheduled runs, causing many incorrect sign-in attempts. If this error occurs regularly, work with your IT administrator to review sign-in attempt logs and account lockout policies.| |
| 66 | +|LogonTypeNotGranted|400|Unattended|For more information, see [troubleshooting documentation for logon type not granted](logon-type-has-not-been-granted.md).| |
| 67 | +|UnallowedTenantForConnectWithSignIn|403|Attended|This error occurs when using a [connect with sign-in](/power-automate/desktop-flows/desktop-flow-connections#connect-with-sign-in-for-attended-runs) connection on an Active Directory (AD) domain-joined machine without adding your tenant to the allowlist. </br> For more information, see ["UnallowedTenantForConnectWithSignIn" error in a Power Automate desktop flow](troubleshoot-unallowed-tenant-for-connect-with-sign-in.md).| |
0 commit comments