​@MLand A bit more information, please. Is this an on-premises control room? What version of control room? 

Automation 360 build 37468. 

Thanks

​@MLand Is this an on-prem or cloud-based control room?

Cloud based.

Hi ​@MLand,

 

Control Room slowness in the cloud can be caused by several factors. Here are common reasons and considerations:

1. Cloud Service Performance or Maintenance:

   • Cloud providers may have ongoing maintenance or temporary performance degradation affecting responsiveness.
   • Check Automation Anywhere’s status page or support announcements for any reported outages or maintenance windows.

2. Network Latency or Local Connectivity Issues:

   • Your internet connection speed, latency, or local network issues can impact Control Room responsiveness.
   • Try accessing Control Room from a different network or device to isolate the issue.

3. Browser Performance:

   • Browser cache, extensions, or outdated versions can slow down Control Room UI.
   • Clear browser cache, disable unnecessary extensions, or try a different browser.

4. Control Room Load:

   • High user activity or heavy workloads in your Control Room tenant can cause slower response times.
   • This can be transient based on peak usage times.

5. Large Data or Logs:

   • Excessive logs, large numbers of bots, or heavy audit data in your Control Room account may slow down UI operations.
   • Consider archiving old data or cleaning up unused bots or logs if possible.

If issue persists, raise a support ticket including details of slowness and timestamps.

Another example of strange things going on - control room shows 2 bots running on 1 machine which is not happening. In this case - the bottom of the 2 had already failed. But this view is after multiple page refreshes.

To further explain, the 2nd job then does not show in the bot runner history. You can go in and find it in the audit log, showing failure. 

​@MLand Thanks. That’s a lot more information!

What concerns me is the bots appearing to run on the same bot runner at the same time. This makes me think we have a duplicated file that records the control room information on the bot runner machines. This can cause duplication of machine names to happen. (Think: Duplicating VMs that already had the bot agent configured and running.)

For all your bot runners, I would recommend putting the following into a batch (.BAT) file and running this as adminstrator (right-click, Run as Administrator). It will disconnect the bot runners from the control room. Then, manually re-connect the bot agent to the control room (log in, connect to local machine).

@echo off
net stop "Automation Anywhere Bot Agent"
del /f /q c:\windows\system32\config\systemprofile\appdata\local\automationanywhere\*.*
net start "Automation Anywhere Bot Agent"

===================================================================

Since the cloud-based control room is kind of a black box, I might turn my attention to the bot runner logs next, which are on the bot runners themselves.

C:\ProgramData\AutomationAnywhere\BotRunner\Logs

There’s no “magic bullet” or specific log that will tell us everything. Look through these files and see if there are any events around the time you expect that look odd. Feel free to report odd events here.

===================================================================

Let me know if that helps. For faster response, email me at aaron.gleason@automationanywhere.com 

​@MLand if you found Aaron’s explanation helpful, please mark it as best answer, thanks!