Description

If a job (not a specific instance) is terminated, and one or more other jobs are waiting for execution in the queue (due to queue limits), the adTempus service goes into an endless loop, using all available CPU time.

This problem was resolved.