I have two jobs, one runs every 2 hours, starting at 12:00 am, the other runs every 2 hours starting at 1:00 am. After we installed patches on our system, we rebooted, and from that time on, both of my two jobs ran on the same hour, on the evens. It's almost like the job wasn't smart enough to relize I set the start time to 1:00 am, which should ensure the job to run on the odds and not the evens. I ended up having to adjust my start time for it to work correctly again.

Is this a known issue? I am currently running VisualCron 5.1.6, and plan on upgrading to 5.5 very shortly.

thanks

Hard to say what happened. But in order to reproduce we need the exact start time and settings and the exact time when you noticed this.

---

Below are some lines of the previous days log, May 01, 2010, and May 02, 2010, as well as the start.

May 01, 2010:
5/1/2010 11:00:08 PM Debug Next execution (2) for job 'CWH FTP Monitor (AVRY Special)' is: 5/2/2010 1:00:00 AM
5/1/2010 11:00:08 PM Info Job completed: CWH FTP Monitor (AVRY Special)

May 02, 2010:
5/2/2010 12:36:47 AM Debug Next execution (6) for job 'CWH FTP Monitor (AVRY Special)' is: 5/2/2010 2:00:00 AM

Startup:
Attached.

As for the settings, are you requesting just the job export?

I think one reason for this is that interval timer is not bound to any specific even or uneven hour and when you restarted it was recalculated with new DST settings. If you want to be sure that you get the same hours at restart (recalculation) you should use the custom time trigger. It is absolute while the other one is more relative.

---

I would have assumed that would be. I was under the impression, not sure if others as well that if you have it set to a start time of say 1:00, run every 2 hours, the calculations should always be based off that 1:00 start time. I understand setting the schedule based on custom would correct this issue, but would think it should be designed that if you have that start time at X time, the schedule should always be based off of that automatically.

I am now changing all my jobs, minus my time change jobs (as the custom doesn't allow for this, and now concerned if they might get affected by this) to be a custom trigger.

thank you

There is another value as well and that is the date. Let say you configured the Job a long time ago then it will try to step forward from that date. Just to be sure here, if you want even or uneven interval - please use the Custom Time Trigger.

---