Working with Workload Objects › Workload Objects › Conditional Jobs

Conditional Jobs

The server completes an Application after all jobs in the Application are complete or are bypassed. Applications can contain conditional jobs that may not run when selected to run.

When all non-conditional jobs in an Application complete, the server bypasses all conditional jobs, regardless of their state, and marks the entire Application complete.

Note: You can resubmit failed conditional jobs provided the Application is not complete.

Example: Optional Predecessors

By default, a job has to wait for all its predecessors to complete or be bypassed before it can run. However, one or more of the job's predecessors may be optional.

Job A and job B are conditional jobs. Job C runs when either job A or job B completes. After job C completes, you want the server to bypass job A or job B if they are not complete.

One of the following will occur:

• If job A completes before job B, job C does not wait for job B to complete. If job C completes before job B, the server marks the Application complete and bypasses job B.
• If job B completes before job A, job C does not wait for job A to complete. If job C completes before job A, the server marks the Application complete and bypasses job A.
• If job A and job B complete before job C, as soon as job C completes, all jobs are complete and the server marks the Application complete.

More information:

Define a Conditional Job