|
<< Click to Display Table of Contents >> Navigation: General Functions > Timed Operations > How the timer works |
Timed operations can be set to run at various intervals. The logic that determines if and when a timed operation is to kick off the schedule, or if the job's time window has come active, and the job has never run before, it will be run on the very first hourly interval which it is supposed to based on its settings.
The underlying time base is one hour. Every hour on the hour the MIE timed operations manager checks the schedule of all timed operations jobs. Every job that has reached its appointed time to run is kicked off by the timed operations manager.
Only active jobs (with the Job is active box checked) will be run. Also, only jobs with a Date this event begins earlier in time than the current date, and a Date this event ends later in time than the current date, will be run.
The logic for determining if a job will be run is as follows:
(the number of frequency events, such as hours or days, is variable and is specified in the This event runs every input box. The number entered will be referred to as <number> in the following table.)
Frequency |
Logic |
minute(s) |
(Reserved for ESI Admins). The job will be run when <number> minutes have passed since the last successful run. |
hour(s) |
The job will be run when <number> hours have passed since the last successful run. |
day(s) |
The job will be run when <number> x 24 hours have passed since the last successful run. |
week(s) |
The job will be run when <number> weeks have passed since the last successful run. |
month(s) |
The job will be run when <number> months have passed since the last successful run. |
quarter(s) |
The job will be run when <number> quarters have passed since the last successful run. |
year(s) |
The job will be run when <number> years have passed since the last successful run. |
In all cases, if a job has been newly added to the schedule, or if the job's time window has come active, and the job has never run before, it will be run on the very first hourly interval.
Understanding Start Times and Exclusion Times.
The Start Time may be best described as the timed operation’s time that it will start at, or as soon as possible afterwards once the system can add it to be run.
The Exclusion Times are used to stop timed operations from running in a given time range.
(Note: The Exclusion Times are required whenever the frequency to run a timed operation is set to Hours or Minutes.)