Education & Training
Services & Support
CA Automic Community
CA Automic Workload Automation
to create and rate content, and to follow, bookmark, and share content with other members.
why does "waiting for parallel task" take up a queue slot?
Discussion created by
on Jul 17, 2017
on Jul 18, 2017 by SamahSohrab607228
Show 0 Likes
We have a job that has 10 executions waiting for parallel task. These 10 jobs are taking up Active Queue slots. Is this a bug or a setting that we can fix?
This content has been marked as final.
Show 2 comments
(Required, will not be published)
Jul 18, 2017 7:57 AM
Thats behavior by design - and in my opinion its logical that a job checks for queue slots and afterwards for parallel clause.
Show 0 Likes
Jul 18, 2017 11:40 PM
I think it should be the opposite. If a job is waiting to run for ANY reason, then it shouldn't take up a queue slot.
It makes no logical sense to me that a job that is in a "waiting" state should be taking the position of an "active" job. Currently, the Active c_period objects don't take up a queue slot and those have a status of "active"
If you want the process to stay similarly the same then it should be AE checks a queue slot, then checks max parallelism, and then removes the job from the queue if it is stuck waiting (or it opens a queue slot).
Show 1 Like
Retrieving data ...
Components automatically installable and configurable
CA20190117-01: Security Notice for CA Service Desk Manager
Upgradation from CASM 12.7 to 17.1
After ticket Creation from Employee ,Employee unable to open tickets
SSL Handshake Exception