Essentially he wants us to make sure that each job in that schedule has 'repeat until terminated' checked.

(And yes, of course they are)

My hunch is that it has to do with some condition where the 'imager' tab wants to keep going to finish the x images in the sequencer, and at the same time, the scheduler (greedy?) wants to stop that job in order to keep the number of images of the (four) jobs roughly equally fast growing.
It happened before only with the first job, the subsequent jobs go on very well. That's likely because the 'number of required images' is equal to the number of images in that sequence.

Cheers!

Read More...