[Anthill-pro] Secondary workflow runs on each agent in sequence instead of in parallel

[Peter Steele]

I ended up filing a ticket on supportal. The problem is by going to the workflow definition for the secondary and setting the "Iterate Job" config for the job steps you want to run in parallel. You can specify whether you want parallel execution and if you do how many parallel jobs to allow (or all if you don't want to limit it). The default for this new feature is to run the job on the selected agents in sequence instead of in parallel. I think the upgrade process should have set this option to parallel execution to mirror the behavior in 3.5.2.

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of emerson cargnin
Sent: Monday, November 23, 2009 6:50 AM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Secondary workflow runs on each agent in sequence instead of in parallel

Hi Peter

I had the same problem. I also tried changing the lock, but no improvement.

If you find out something please let me know.

regards
emerson

2009/11/23 Peter Steele <psteele at maxiscale.com>:
> I have a secondary workflow where the user can select multiple agents on which the process is to run. Before upgrading to 3.7.1 the job would run on each agent in parallel. Now though the job runs sequentially on each agent at a time. I've set the the lock duration to "workflow" but this doesn't seem to have an effect. This is clearly different behavior than in 3.5.2, but I'm unclear how to configure the secondary to make it work like it used to. Any suggestions?
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro