Unable to perform rdp or Bot launched crashed

Update : I have rebooted the VM but it does not seem to change anything

I have switched the deployment option to multiple users but I got anew the error  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.

Hi ​@Augustin,

A common reason for this issue is multiple users being connected to the same Bot Runner device at the same time. When that happens, the device can hit its maximum allowed session limit, which causes RDP failures or unexpected bot crashes.

I recommend checking:

• How many user sessions are currently active on the impacted Bot Runner machine
• What the maximum allowed session count is for that server
• Whether any disconnected but still active sessions are consuming resources
• Whether the auto‑login configuration is correctly pointing to a single dedicated bot user (which already looks good in your setup)

Once the session count is corrected and only the intended bot user is active, the issue usually stabilizes.

Hi Dineshkumar,

AWS Workspaces only allows for one connection at the same time and I have tried all the different settings it seems.

Hi ​@Augustin , 

The issue happens because the auto‑logoff on the Bot Runner machine doesn’t trigger properly, leaving an active session behind. When that session stays open, the next RDP attempt or bot execution can fail or crash.

Adding a System → Logoff action as the final step in the bot is a practical workaround. It forces the session to close cleanly every time the bot finishes, ensuring the next run starts fresh without leftover user sessions.