Startup Trigger
A Startup Trigger is a trigger that causes a job to be executed each time the adTempus service is started. This may be because the computer is being started, or because the adTempus service was restarted.
The adTempus service cannot determine whether it is being started as part of computer startup or because the adTempus service was stopped and restarted for some other reason. Therefore you may need to perform additional configuration to prevent duplicate processes, as discussed in the sections below.
Avoiding Duplicate Processes
If adTempus is stopped and restarted for a reason other than a computer restart, the program started by the job may still be running when adTempus restarts. When you use the Startup Trigger you should also use process conditions, the Process Execution task's Skip if already running option, or some other safeguard to make sure that your scheduled tasks do not get re-executed when they should not.
Suppose you have a job with a Startup Trigger that is configured to start OrderMonitor.exe, which is intended to run as long as the computer is running. When Windows starts, it starts the adTempus service, which starts OrderMonitor.exe.
Now suppose the adTempus service gets stopped and restarted for some reason (such as a software update). When the service starts again, it will again run the startup job, which will start OrderMonitor.exe again, unless you have configured one of the options discussed above.
Suppressing Startup Jobs
You can prevent adTempus from executing Startup Triggers by using the -nostartup Start parameter when starting the adTempus service from the Windows Services tool. (See the Service Startup Options topic for more information.)
When you specify this option, all Startup Triggers will be ignored.
