Interval

Less than 60 minutes


You need to specify the number of minutes/seconds after which the job should run again. If less than one hour is specified, the job pauses for the specified time and then restarts.

The following figure shows the sequence of events for an interval setting of "30" minutes and a job runtime of 10 minutes.


images/download/attachments/164332814/Intervall_1-version-1-modificationdate-1704700372355-api-v2.png


(1) A job is started at 08:00 and runs for 10 minutes. After that, the profile pauses for 30 minutes.

(2) A job is started at 08:40 and runs for 10 minutes. After that, the profile pauses again for 30 minutes.

From 60 minutes


For interval times bigger than "60" minutes, another algorithm comes into effect.

The next start time is calculated at the moment of saving a profile, after a cron job run or when the Integration Server is started. The calculation is based on the current date and the minute of the "Valid from" value in the profile.

Examples where "Valid from" is not on the full hour:


  • Valid from value is 2005-07-12 14:44:50.567, the interval is set to 120 minutes.

  • Times of calculation: 2019-10-12 15:00:00.0, 2019-10-12 15:59:59.999, 2019-10-12 16:00:00.0, 2019-10-12 16:00:00.001.

  • Calculated times: 2019-10-12 16:44:00.0, 2019-10-12 16:44:00.0, 2019-10-12 17:44:00.0, 2019-10-12 17:44:00.0.


Examples where "Valid from" is on the full hour:


  • "Valid from" value is "2005-07-12 00:00:00.0", the interval is set to "120" minutes.

  • Times of calculation: "2019-10-12 15:00:00.0", "2019-10-12 15:59:59.999", "2019-10-12 16:00:00.0", "2019-10-12 16:00:00.001".

  • Calculated times: "2019-10-12 17:00:00.0", "2019-10-12 17:00:00.00", "2019-10-12 18:00:00.0", "2019-10-12 18:00:00.0".


Note: At an interval of "60" minutes, the result may be surprising. Calculated times: "2019-10-12 16:00:00.0", "2019-10-12 16:00:00.49", "2019-10-12 17:00:00.0", "2019-10-12 17:00:00.0". The waiting time can sometimes be only a few milliseconds long and here the result would theoretically be one millisecond, but everything smaller than 50 is replaced by "50".

Note: A start time expires if the runtime of the cron job is longer than the specified interval time.