On the control room I would go to Activity->In Progress and stop any currently running processes you see there.

If that doesn't work try restarting the automation anywhere service on the machine you are attempting to run the bot on.

Hi @SVS Guptha​ ,

This usually happens when you start and stop a deployment, but the deployment is still active.

Restarting the Bot Agent usually resolves it(Ctrl+Shift+Esc -> Services -> Automation Anywhere Bot Agent -> Restart)

Kind Regards,

Ashwin A.K

Hi,

This scenario is addressed in Automation 360 v.17; please upgrade to Automation 360 v.17 or later versions for a permanent fix to the issue.

For versions earlier to Automation 360 v.17, please follow the steps mentioned below,

https://apeople.automationanywhere.com/s/article/There-is-already-an-existing-deployment-in-progress-for-this-user-session-If-the-problem-persists-please-contact-your-system-administrator/p>

Regards,

Saba