Hi,

If you want to run a maximum number of jobs in parallel then you should add the WaitForJobCompletion activity inside the ForEach loop. In this way the numberOfParallel executions will control how many jobs can be running at once. As each iteration completes the thread will free up allowing another to start until they are all complete.

If you are getting an error with this approach then at a guess it’ll be to do with collecting the job id and passing it to the WaitForJobCompletion activity … should be able to tell by checking workflowEngine.log

The jobId input for the WaitForJobCompletion task accepts a list of job ids. This means you can also create multiple jobs and pass a list of the job ids to the activity. For example you could use the foreach loop to submit the jobs and then monitor those jobs for completion after they have all been submitted. In this case the numberOfParallelExecutions will control the maximum number of new job requests that can submitted in parallel but the loop won’t wait for any to complete eg it’ll just submit each and move on to the next.

Example of this:

Inside the foreach loop…

• start the job
• get the job id returned
• add the job id to a list outside the foreach loop (you can create an List<Integer> workflow variable for this)

You then add the WaitForJobCompletion after the foreach loop. Set the jobId input to the workflow variable you are storing the job ids in.

Hope that helps