Skip to main content
Question

Deployment Failure: Max RDP session count reached

  • December 17, 2025
  • 2 replies
  • 8 views
A
Forum|alt.badge.img+1

Hi,

 

We have scheduled a bot every 15 minutes, it works fine for couple of days and then the deployment start to fail. The frequency of failure is less at starting and then increases gradually to a point where each deployment gets failed.

Can someone tell how to resolve this issue?

 

The error msg that we see is - “

Error message:

Unable to perform rdp for the user as we have exceeded the maximum session count. This may be due to multiple reasons. To continue, please Make sure you logout from sessions that are not required at the moment.

Then, try to run the bot again. If you continue to see this message, please contact your system administrator.

”

2 replies

A
Forum|alt.badge.img+1
  • akshay.darmwal
  • Author
  • Cadet | Tier 2
  • December 17, 2025

Hi,

 

We have scheduled a bot every 15 minutes, it works fine for couple of days and then the deployment start to fail. The frequency of failure is less at starting and then increases gradually to a point where each deployment gets failed.

Can someone tell how to resolve this issue?

 

The error msg that we see is - “

Error message:

Unable to perform rdp for the user as we have exceeded the maximum session count. This may be due to multiple reasons. To continue, please Make sure you logout from sessions that are not required at the moment.

Then, try to run the bot again. If you continue to see this message, please contact your system administrator.

”

We have tried everything from the VM prespective and the issue seems to from control room.

Tamil Arasu10
Most Valuable Pathfinder
Forum|alt.badge.img+18
  • Tamil Arasu10Most Valuable Pathfinder
  • Most Valuable Pathfinder
  • December 17, 2025

 

Could you please try the following the steps.

  • Enable Auto-Logout After Bot Execution

    • In Control Room → Devices → Edit Device Settings, ensure:
      • “Log off user after bot execution” is enabled.
      • This forces the runner to close the session after each run.

  • Check Windows Group Policy

    • Configure Idle Session Timeout:
      • gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Session Time Limits
      • Set End a disconnected session to a short time (e.g., 1–5 minutes).

  • Increase Maximum RDP Sessions (Optional)

    • If multiple bots share the same runner, consider increasing the session limit or using multiple bot runner accounts.

  • Use Bot Runner Pooling

    • Instead of one device handling all runs, create a device pool so sessions are distributed.

  • Schedule Cleanup

    • Run a script or use Automation Anywhere’s Device Health Check to terminate stale sessions periodically.

  • Check Control Room Settings

    • Go to Administration → Settings → Device Management and confirm:
      • Force logoff after bot execution is enabled.
      • Session reuse is disabled if causing conflicts
_Tamil_
Terms & ConditionsCookie settingsAccessibility statement