![]() |
![]() |
We are currently migrating this forum over to our HelpSystems domain. Please post all new threads in our new HelpSystems Community Portal. |
![]() |
|
![]() |
AutoMate Discussion | ![]() |
Topic Title: Incorrect running workflows count causes all new workflows to get stuck in the queue Topic Summary: Created On: 05/01/2015 10:29 AM Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
||||||||||
We've noticed that every now and then, the running workflows count in the Dashboard tab will be at the max (according to our throttling settings) even though no workflows or tasks are running, and this causes every subsequent workflow that triggers to get queued until we restart the Execution Service in order to restart the running workflows count to 0. We thought this was an issue with v9.0.2.8 because we could see that BPATask processes hung, and killing them brought the running workflows count down again (for the record, only as long as the BPATask process was still tied to a parent BPA_TS process). After upgrading to v9.0.5.4 we see no more hung task processes so we assumed this issue was gone, but we already had one instance of the running workflows count "maxing out" and causing everything else to queue. Is this a known issue? Is there a patch for it? We already have a patch installed to address high CPU consumption issues.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hello Alejandro, When you see the BPATask processes hung, are they all running with a specified user name or is ther one running as the SYSTEM user? Does this happen when the machine is locked or logged off?
This is not a known issue. It may be that BPA is trying to log in to run a specified task and is unable to.
------------------------- Mary Manzano | Technical Consultant AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
As I said, after upgrading to v9.0.5.4, we don't see hung BPATask processes anymore (not sure if *that* is a bug, though...). But all of our tasks are configured to run as the same domain account, and the BPATask processes that show up and finish correctly do show up running as that one. This happens both when the machine is logged off and when it is locked.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hello Alejandro,
Please let us know your availability for setting up a Remote Session so we may see this issue first hand. If this is possible please send an email over to automate.support@helpsystems.com. AutoMate Technical Support is available from 6am to 5pm Monday through Friday Pacific time (GMT -7). Toll Free 888.786.4796 Note: Please reference the Topic Title of this forum thread in the subject. "Incorrect running workflows count causes all new workflows to get stuck in the queue"
------------------------- ![]() Valentineo McGowan | Technical Consultant AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1 213.738.6966 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
When we see it again I'll contact you for the remote session.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Alejandro,
We look forward to hear from you.
------------------------- ![]() Ricardo Castaneda | Principal Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 |
||||||||||
|
||||||||||
![]() |
||||||||||
We've noticed that every now and then, the running workflows count in the Dashboard tab will be at the max (according to our throttling settings) even though no workflows or tasks are running, and this causes every subsequent workflow that triggers to get queued until we restart the Execution Service in order to restart the running workflows count to 0. We thought this was an issue with v9.0.2.8 because we could see that BPATask processes hung, and killing them brought the running workflows count down again (for the record, only as long as the BPATask process was still tied to a parent BPA_TS process). After upgrading to v9.0.5.4 we see no more hung task processes so we assumed this issue was gone, but we already had one instance of the running workflows count "maxing out" and causing everything else to queue. Is this a known issue? Is there a patch for it? We already have a patch installed to address high CPU consumption issues. Was there ever a resolution to this issue? I think it's what might be happening to us now.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Brian,
Have you noticed any type of pattern with this issue? Does it occur with all workflows or is it specific?
------------------------- ![]() Ricardo Castaneda | Principal Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 |
||||||||||
|
FuseTalk Enterprise Edition v4.0 - © 1999-2021 FuseTalk Inc. All rights reserved.