Introduction to Operators › Common Properties of all Operators › Execution Settings (All Operators) › Loop and Timeout Scenarios

Loop and Timeout Scenarios

If an operator is in a loop and the timeout is configured, then the following scenarios take place for the selected actions:

Action

Select from one of the following actions:

Continue

If selected, the process proceeds in the following manner after a timeout:

1. The next iteration executes.

2. The post-execution code only runs if the iteration is complete.

Using the OverallLoopDuration dataset variable to continue looping an operator that times out:

At the end of execution, the OverallLoopDuration contains the number of seconds from the start of the first iteration until the end of the last iteration. If the operator times out, the OverallLoopDuration does not contain the number of seconds from the start of the first iteration until the time the operator times out.

Reset

If selected, the process proceeds in the following manner after a timeout:

1. The iteration resets (that is, the particular iteration starts executing again).

2. The post-execution code executes only when the current iteration completes (not when the iteration was reset).

3. The next iteration executes only when the iteration completes.

Note: If Reset is selected, then the Target Date option is disabled in the Type drop-down list.

Using the OverallLoopDuration dataset variable to reset a looping operator that times out:

If you set an operator to loop with a timeout action of Reset, CA Process Automation checks the loop condition when moving from one iteration to another. The loop condition is not checked when resetting an iteration. Also, the OverallLoopDuration contains the number of seconds from the start of the first iteration, including the time spent in all the reset iterations. Iteration resets do not affect the OverallLoopDuration.

Abort

If selected, the flow proceeds in the following manner after a timeout:

1. The iteration aborts.

2. The post-execution code executes.

3. The next iteration executes.

Abandon

If selected, the process proceeds in the following manner after a timeout:

1. The iteration continues to run in detached mode.

Note: An instance of a process started in detached mode has no parent relationship to the process that started it and is the root process in any call sequence originating from that process.

2. The post-execution code executes.

3. The next iteration executes.