MaxRDSessionDurationReached or SessionHasLoggedOffWithMaxIdleTime occurs during a desktop flow run

Artikkeli
12/11/2024

This article provides a resolution for error codes that occur during a desktop flow run in a cloud environment in Microsoft Power Automate.

Symptoms

When you run a desktop flow in a cloud environment in Power Automate, the flow run might fail with one of the error codes that indicates the registry value name and its specific registry path.

{ 
    "error":{
        "code": "MaxRDSessionDurationReached",
        "message": "The session 5 duration (1856000 milliseconds) exceeded the one set in registry for MaxConnectionTime with value 1200000 in registry path Software\Policies\Microsoft\Windows NT\Terminal Service."
    } 
}

{ 
    "error":{
        "code": "SessionHasLoggedOffWithMaxIdleTime",
        "message": "The session 5 duration (1856000 milliseconds) exceeded the one set in registry for MaxIdleTime with value 1200000 in registry path Software\Policies\Microsoft\Windows NT\Terminal Service."
    } 
}

Cause

The error message indicates that the remote desktop session was logged off because it exceeded the time limit specified in the registry (MaxConnectionTime or MaxIdleTime). This issue happens when the session time limit in the registry setting is shorter than the time needed to complete the desktop flow.

Resolution

To solve this issue, contact your administrator to change the settings by using one of the options.

Option 1: Through the Local Group Policy Editor

Verify the group policy settings to ensure no configurations are set to sign out of the remote desktop session due to time limits. You can do this by opening the Local Group Policy Editor and navigating to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Session Time Limits.

If the error message points to the MaxConnectionTime registry value, check the Set time limit for active Remote Desktop Services sessions setting. If it's enabled, disable it or set the Active session limit value to Never.
If the error message points to the MaxIdleTime registry value, check the Set time limit for active but idle Remote Desktop Services sessions setting. If it's enabled, disable it or set the Active session limit value to Never.

Option 2: Through the Registry Editor

Open Registry Editor and find the registry value name from the error message in the specified registry path under Computer\HKEY_LOCAL_MACHINE\.

For example, Computer\HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Service

If the MaxConnectionTime or MaxIdleTime registry value exists, set it to 0 (zero), which means it's unlimited.

Note

The registry value can also be deleted or set to a value greater than the maximum execution time of the desktop flow.

Registry value name	Description
MaxConnectionTime	Specifies the maximum time (in milliseconds) that a remote desktop session can remain active, regardless of activity.
MaxIdleTime	Specifies the maximum time (in milliseconds) that a remote desktop session can remain idle (without user input, such as keyboard or mouse activity) before it's logged off.

Jaa