Two options common to all conditions determine whether and how adTempus should wait for the condition to be satisfied.
The Condition Wait option tells adTempus whether to wait for the condition.
Do not wait for condition to be met. adTempus will test the condition only once. If the condition is not immediately met, the condition fails.
Wait until the condition is met. adTempus will keep checking the condition every few seconds until it is met.
Wait up to __ minutes for the condition to be met. adTempus will wait, up to the number of minutes you specify, for the condition to be met. If the condition is not met at the end of that time, it fails.
The Once satisfied, do not re-evaluate for this instance option tells adTempus whether to keep checking the condition once it has been satisfied. This option is only relevant if there is more than one condition for the job or step.
When adTempus must wait for conditions to be satisfied, it polls (re-checks) the conditions at an interval of a few secondss. If the Once satisfied, do not re-evaluate for this instance option is set for a condition, adTempus does not continue polling that condition once it has been satisfied. If the option is not set, adTempus does continue polling the condition once it has been satisfied, which means that it is possible for the condition to become "unsatisfied."
The following example illustrates these options.
Your job "Data Copy" has two conditions:
Condition 1: A File Condition specifying that target file "c:\data\datafile1.dat" must exist.
Condition 2: A Job Condition specifying that target job "Data Extract" must have completed successfully.
Both conditions are configured to wait up to 5 minutes for the condition to be satisfied.
Job "Data Copy" starts and adTempus checks the two conditions. It finds that:
File "c:\data\datafile1.dat" exists (Condition 1 satisfied)
Job "Data Extract" is still running (Condition 2 is not satisfied)
Because both conditions are configured as waitable, adTempus will wait for the second condition to be met. One second later it checks the conditions again and finds that:
Job "Data Extract" has completed successfully (Condition 2 is now satisfied)
However, file "c:\data\datafile1.dat" no longer exists. Here is where the Once satisfied, do not re-evaluate for this instance option comes into play:
If this option is checked, the condition remains satisfied even though the file no longer exists. Since both conditions are now satisfied, the job proceeds.
If the option is not checked, the condition is no longer satisfied, because the file does not exist. adTempus will continue waiting until both conditions are satisfied or until the wait timeout elapses.