Job Condition Instance Example

This example illustrates the behavior of the Job Condition based on the four available Instance options.

Suppose you are making job "Data Copy" dependent on job "Data Extract," with the Rule set to "Job must have succeeded" (that is, "Data Copy" cannot run until "Data Extract" has run successfully).

At 12:00 PM instance 312 of job "Data Copy" finishes.

At 12:15 PM instance 403 of job "Data Extract" finishes successfully.

At 12:30 PM instance 404 of job "Data Extract" fails.

At 12:45 PM instance 313 of job "Data Copy" starts.

• If the Instance is set to "The most recent instance," the condition is not met, because the most recent instance (404) failed.
• If the Instance is set to "The most recent instance since the previous execution of job," the condition is not met, because the most recent instance (404) failed.
• If the Instance is set to "Any instance since the previous execution of job," the condition is satisfied, because instance 403 succeeded.

At 1:00 PM instance 405 of job "Data Extract" finishes successfully.

At 1:15 PM instance 314 of job "Data Copy" starts. Regardless of which instance you have selected, the condition is met.

At 1:30 PM instance 315 of job "Data Copy" starts (note that "Data Extract" has not run again in the interim).

• If the Instance is set to "The most recent instance," the condition is met, because the most recent instance (405) succeeded. However, "Data Copy" has not been run since the last "Data Extract," so you probably would not want the "Data Copy" to run again yet.
• If the Instance is set to "The most recent instance since the previous execution of job," the condition is not met, because "Data Extract" has not been run since the last time "Data Copy" was run.
• If the Instance is set to "Any instance since the previous execution of job," the condition is not met, because "Data Extract" has not been run since the last time "Data Copy" was run.