Symptoms

If a schedule is configured using a "wraparound" scenario, where the effective time period for the schedule crosses midnight, adTempus will fail to run jobs during a portion of the schedule period.

Example 

A Schedule Trigger is configured to run at a specified interval, with a start time that is later in the day than the end time (for example, between 6:00 am and 4:00 am). The intended behavior is for the job to execute except during the period from 4:00 am to 6:00 am. Instead, adTempus will miss executions from 12:00 am to 4:00 am, and will only execute the job from 6:00 am to 11:59 pm.

Workaround

This scheduling scenario can be accommodated by using two separate schedules on the Schedule Trigger:

• The first Schedule is configured to execute the job at the desired interval between 12:00 am and 4:00 am.
• The second Schedule is configured to execute the job at the desired interval between 6:00 am and 11:59 pm.

Status

• adTempus 3
  This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.