Overview

Stop Policies can be set by selecting the Stop policy tab when saving the job. The stop policy works in conjunction with the job schedule. It determines when a job should stop running. If a stop policy is not set for a scheduled job, the job will continue to run according to its scheduled time until it is manually stopped or removed. Once a job meets the stop policy, its status changes to "Complete." You can set multiple stop policies. In this instance, the job will stop running as soon as it meets one of the set stop policies. 

Stop after a number of total runs

Use this option to set the total number of job runs that should occur. The job will only run the specified number of times.

Stop after a number of runs with no changes

Use this option to stop the job once the specified number of runs has occurred without any changes to the content; all content has been transferred successfully. Job executions that detect no changes do not need to be consecutive to increment your stop policy count. If new content is added to the source and the job runs again, this will not increment your stop policy count.

Stop after a number of failures

Use this option to stop the job after the set number of failures is reached. Job executions that detect failures do not need to be consecutive to increment your stop policy count. Most failures are resolved through automatic retries. If the retries fail to resolve the failures, then manual intervention is required. This policy removes the job from rotation so the issue can be investigated.

This stop policy does not include when jobs fail to start; only failures logged during the job run count toward the stop policy. When a job fails to start, it is generally the result of a configuration issue.

Stop after a specific date

Use this option to set a specific stop date for the job. The job will run according to the schedule and stop at midnight on the specified date.