Posted Fri, 19 Oct 2018 03:04:34 GMT by

 We are on Automate Enterprise 11.0.17 and over a 10 day period we've noticed CPU utilization slowly increase to 50pct, after 20 days it is in the 90pct range. We have around 60 workflows. The most frequent of which trigger ever 15 minutes.Is there any way to prevent this, as it eventually starts to degrade performance? 

Posted Fri, 19 Oct 2018 23:46:37 GMT by

Hello Barnes,


Are all components installed on the same machine? If not can you describe your setup?


Are there any errors in the windows Event Viewer (under application)?


What types of workflows are you running (SQL, interactive, background)?

Posted Sat, 20 Oct 2018 01:58:00 GMT by

Yes management, execution, and agent all run on the same machine (Windows 2012 R2 Standard).


We do see errors from time to time with one workflow, it downloads files from an SFTP that sometimes contain invalid characters and it causes "AML is Invalid" errors in the event log.


Most of our workflows are triggered by schedule conditions (we have 60 or so conditions and workflows), we do use several file watchers. Most tasks invoked by the workflows move files, invoke other applications or scripts, and a few query SQL datasources. 

Posted Thu, 25 Oct 2018 05:17:14 GMT by

Hello Barnes,

Which process is taking the CPU when the issue occurs? Is it BPA_Man.exe? BPA_Exec.exe?

Do you have any errors regarding workflows getting stuck or not executing properly?

You mention you had tasks that use FTP actions and SQL queries. When opening the FTP connection, do you have a "close connection" step? Same for the SQL connections?

Posted Tue, 30 Oct 2018 02:53:14 GMT by

BPA_Exec.exe is the task that ends up consuming the CPU. After a reboot though it will remain in low usage for days or even weeks. Other than the error mentioned above, we don't typically see too many (unless a remote SFTP site is down etc). We typically close FTP / SQL connections. 

Posted Sat, 03 Nov 2018 03:27:12 GMT by

Hi Barnes,

First and foremost, I recommend updating to the latest version of Automate Enterprise. A lot of corrections have been applied since your version. I have reviewed your support cases and I do not see a case referencing a similar issue. I recommend, on top of updating, to open a support case so that we can schedule a remote session with you to further troubleshoot. 



Posted Tue, 13 Nov 2018 05:50:44 GMT by

Hi Barnes,

I have been working with Automate support on this same type issue as well. The latest release was to address the BPA_MAN.exe memory "leak" and it appeared to do so. Unfortunately the release was unstable in our environment and I had to revert back to 11.1.1. I still had the issue with the BPA_EXEC.exe "leaking" memory though. I have support tickets open on both items. Thought I would share :)

Posted Wed, 14 Nov 2018 00:14:29 GMT by

We see both elevated memory and cpu usage. It caused the server to become unresponsive over the weekend. From what I can tell it appears to occur when a user is logged into management studio for extended periods of time. When we see it typically a user will RDP to the server, login to the management tool, disconnect from RDP without signing out, and leave the tool open for several hours or more.

Posted Tue, 20 Nov 2018 06:17:29 GMT by

Hi Barnes,

We have had some customers report elevated memory usage in the Management Service process when the SMC is left open and connected for an extended period of time. Depending on your license, you may have Access to the Management Console Sessions feature under the Options/Server Settings page. Here you can enable session time out by users. The timeout is for inactivity. This should help with the situation you are describing. We still would recommend you update to the release to see if the changes made provide relief for the High CPU usage issues.

Posted Wed, 12 Dec 2018 05:46:21 GMT by

As an update I tried to update to and it seems to have broken SSL/TLS, which is a requirement for us. I submitted a ticket and they created a bug case (#24736). 

Posted Thu, 10 Jan 2019 07:48:00 GMT by

Has there been any progress on this? We still aren't able to update due to bug # 24736 (SSL not working in latest version). 

Posted Thu, 10 Jan 2019 09:20:03 GMT by

Hello Barnes,


I do apologize however this issue is still being worked on by our development team. This thread will be updated once the issue has been corrected. 

Posted Tue, 16 Apr 2019 23:38:59 GMT by

As of updating to we are no longer seeing CPU usage "creep" or elevated cpu usage.

Posted Wed, 24 Apr 2019 02:12:42 GMT by

how about the memory leak issue?  I have to restart my automate serves daily or my server will become unresponsive and has to be restarted.

Posted Wed, 24 Apr 2019 02:27:19 GMT by

Which version are you on? On we would get up to 1500MB range before our weekly reboot. Now it seems to sit around 350-450. We are only rebooting monthly at the moment. Out of curiosity, approximately how many workflows are you running? We have about 90 workflows with their own schedule conditions. 

You must be signed in to post in this forum.