Triggers Page
Options on the Triggers page determine when the job will be run.
The Allow job to be triggered by other jobs option that previously appeared on this page has been replaced by the Hold Status setting on the General page.
Triggers
The Triggers list lists the triggers that have been defined for the job. You can add, edit, or delete triggers. See the Triggers topic for information on the available trigger types.
Multiple Instances
The Multiple Instances options determine what adTempus should do if an instance of the job is already running when a new instance is triggered:
- Execute (start a new instance). A new instance will be started. Use this option when it is acceptable for overlapping instances of a job to be running.
-
Do not execute. The job will be skipped.
When a job is skipped due to this setting, no instance is recorded in the job's execution history, but the job's Last Status is set to "Skipped."
- Execute only if the previous instance(s) complete within the specified interval. adTempus will wait for the delay you specify. If the previous instance(s) complete within that time, a new instance will be started. Otherwise the execution will be skipped (as in the previous option).
- Wait for the specified interval, then execute regardless of whether previous instances have completed. adTempus will wait for the delay you specify. At the end of that time, a new instance will be started, regardless of whether previous instances have finished.
- Terminate prior instances, then run. adTempus will terminate (abort) any other instances of the job that are running, then start the new instance.
When you start a job manually using the Execute command or from another job using a Job Control action, you have the option to override these settings and force a new instance to be started.
If the job uses the Terminate prior instances setting and you use the Force a new instance of the job if necessary option when starting the job, adTempus will start the new instance without terminating prior instances.
Update the Cycle ID for this job's scope when the job runs
When this option is checked, adTempus will update the Cycle ID for the job's group (or the nearest parent group that is configured to use Cycle IDs) each time the job is run.
When you are using Cycle IDs, you must configure one job with this option checked to run at the beginning of the cycle. This is what tells adTempus that a new cycle has begun. It updates the Cycle ID for the job group, and that Cycle ID is then assigned to this job and all others that run within the cycle scope.