When observing the Start Time of Time Events during a period, a shift of seconds is observed compared to the expected schedules duration.
For instance a TIme Event that runs every 30 minutes can have the following Start Times:
Expected (hh:mm:ss)
|
Real (hh:mm:ss)
|
00:00:00
|
00:00:44
|
00:30:00
|
00:30:47
|
01:00:00
|
01:00:48
|
01:30:00
|
01:30:52
|
02:00:00
|
02:00:52
|
02:30:00
|
02:30:53
|
...
|
...
|
The delays are caused by 4 factors:
Factor (1) depends on number of jobs to be calculated at Period Turnaround and thus the database performance. Because of (2) and (3) small additional delays can build up. Lastly, because of (3) the delays are pushed forward and can never go down.
Release : v12.2 / v12.3
Component : AUTOMATION ENGINE
If very precise scheduling is needed it is recommended to use the C_PERIOD. This will put the request to launch of the job at the required launch time.
The job will be launched max. 20 seconds after the scheduled launch time.