I'm having a confusing time w/ the scheduler.  One issue I logged here at gemini - basically - if catch up is NOT enabled - the Next start time is always 1/1/1753 12:00:00 AM -- I don't want catch up enabled because the scheduled procuess should only run once per day ... not 3 times if it's catching up (it's sending emails - and catching up will send duplicate emails)

NOW - I have an issue where the same schedule is set to run Every 1 day - and retry every 10 minutes.  If it runs today (7/13/2011) - and when it runs successfully - it reschedules for 2 days out (7/15/2011) 

I'm now running DNN 5.6.3 - and this scheduler MUST run DAILY.    It was running "fine" in DNN 5.2.3 (except for the "catch up" aspect) - anyone else w/ these issues? 

---

---

Andrew Walker

If you enjoy making your own beer and/or wine - be sure to check out http://www.ForemostBrewing.com

I ran into the exact same issue with DNN 5.6.1.  I started my scheduled items out with Catch Up Enabled unchecked an ran into the issue where the Next Start was set at 1/1/1753.  Checking the "Catch Up Enabled" seemed to resolve this problem, but then I noticed that the next start was scheduled for twice the time that I had configured in the schedule.

Turns out, the problem was that I based my custom scheduled item on some code samples that indicated upon successful completion of a scheduled item, you should call Completed() on the SchedulerClient - for example, here is one such article:

http://www.byteblocks.com/post/2011/0...

This is INCORRECT - Completed() is called by the DNN framework and if you call it manually like it suggests in the article above, it will set the Next Start date AGAIN based on the schedule after the framework does it and you end up with double the time.

Honestly, I think the issue here is the scope of the Completed method - it should not be available for direct calling to descendants who inherit SchedulerClient.  Anyways, thought I'd share my findings - hope this helps!