Periodic Jobs not running on time although “Force adjustment on time frame” is set

Document ID : KB000088036
Last Modified Date : 14/04/2018
Show Technical Document Details
Error Message :

Periodic Jobs are not running on time although "Force adjustment on time frame" is set when the start time is 00:15 am and the frequency is set "with a gap…to previous run".
Especially the first interval – 00:15 (and the next 04:15) is jumped over.

  1. A simple Job was created for this (e.g.: a simple Windows Ping job like -n 60)
  2. Let this job run periodically with the following settings:
Frequency | With a gap of: 04:00
Time frame | Between 00:15 and 23:59 + Check set on "Force adjustment on time frame"
Days | Weekdays – Mon, Tue, Wed, Thu, Fri Sat, Sun
Range | Start date: 08.08.2016 – End Date 22.08.2016

The screenshots below illustrate these settings.
  1. The Job is running in the Client_Queue and using a 1:1 copy of the TZ.CET object as a TimeZone object.


The job was initially started on 08.08.2016 13:19:30 (UTC) | 15:20:30 (local time)
The job ran the first time on 08.08.2016 13:19:42 (UTC) | 15:19:42 (local time) and ended at 13:20:41 (UTC) | 15:20:41 (local time)
The Time Switch was at 22:15:14 | 00:15:14 but the job was not executed at that time.

Also not 4 hours later, like set on the time frame Tab in the Period but at 05:23:11 | 07:23:11.

So there is a bigger gap between the last run and the next run after the time switch.

The job runs in the TimeFrame Set beginning with the StartTime or at least with the defined Frequency after the TimeSwitch.
OS Version: N/A
Cause type:
Root Cause: Periodic Jobs are not running on time although "Force adjustment on time frame" is set.
Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Automation Engine 12.0.2 - Available
Automation Engine 11.2.3 – Available
Additional Information:
Workaround :