Job completion verification rules

An Execution operation can be defined as follows:

• Simple Execution: Synchronous operation with no tracking and default abort. The job ends when the job fails or succeeds.
• Complex Execution: Asynchronous operation includes tracking progress and enables you define what happens when the job is to be killed.

Verify operation completion: Enables you to add a new sub step to the operation where you can define an operation to run to identify job completion. For example, where the Execution step started a specific process in the remote application and the operation itself has completed, the process still runs. By defining the Verify operation completion step the operation is executed in a loop (every few seconds) to check against the remote application to see when this process really ends. You can do the following:

• Change the default interval (every 2 seconds) between each completion verification execution that is run, until the completion criteria is matched. You can add a parameter to define different intervals for different parameters for connection profiles or jobs.
• Set retry intervals or timeouts. If the completion process fails, you set the following:
  • Number of times the job retries before failing the step
  • The number of minutes the job retries before failing the step

You can use the output/response handling or Return Code handling to define that the step is completed and fail the job or proceed to next step (if exists), which means that this specific process completes OK. By default, all operations end when the execution ends.

The following procedures describe how to define Command Line, Web Service and REST API job completion verification rules to the Execution operation:

• Defining a Command Line job completion verification rule
• Defining a Web Service job completion verification rule
• Defining a REST API job completion verification rule