Define Job Schedule
During job creation, the final step is to define when the job will run and what criteria will define when it stops.
- Save job will launch the job scheduler
- Save job and run it right now will trigger the job to start immediately. It will run every 15 mins after the last execution completes
Schedule Stop Policies
Stop policies determine when a job should stop running. If none of the stop policies are enabled, a scheduled job will continue to run until it is manually stopped or removed.
The options for the stop policy are:
Stop after a number of total runs
The number of total executions before the job will move to "complete" status
Stop after a number of runs with no changes
The job has run and detected no further changes; all content has transferred successfully.
If new content is added to the source and the job runs again, this will not increment your stop policy count. However, job executions that detect no changes do not need to be consecutive to increment your stop policy count.
Stop after a number of failures
Most failures are resolved through automatic retries. If the retries fail to resolve the failures, then manual intervention is required. This policy takes the job out of rotation so that the issue can be investigated.
Job executions that detect failures do not need to be consecutive to increment your stop policy count.
Stop after a specific date
The job will "complete" on the date defined