Description

This problem still occurred in some cases even after fix CR00005098 in adTempus 4.2. The problem occurred only when:

• A job runs in a Queue that is configured to use Load Balance or Slave mode
• The Queue is configured to check conditions on the Master
• The job has previously been sent to an Agent for execution following a condition check.

On subsequent execution attempts, the job will get stuck in "Waiting for Condition" status.

In addition, if the job is configured to not execute if another instance is already running, the job may be skipped even though no instance is active.