I think I have found a bug in the dnn scheduler. I am however not sure, so perhaps someone can help me out to find the problem at hand....

It looks as if a schedule item is being run more often than configured when it is a long running process. my custom schedule item sends an email, I now receive more emails than expected. and it is getting very irritating receiving the same email more than once...

Here is a more detailed description of my problem:

What I Did:
I Developed a SchedulerClient that sends an email. I added a schedule item in the hosts menu under schedule. And set options of item to run once every day and set "catch up" disabled.

What I Expect:
To receive one email every day due to this schedule.

What Happened:
I receive one but sometimes more than one email! (usually two emails every day)

In the schedule history I see two entries instead of one... And when debug logging is turned on for the DNNScheduler then I see two entries "added to process group.." for this schedule item.

It looks like my schedule Item takes a very long time to process (more than 1 minute) and I think the dnnscheduler thinks the item has not been run so it starts it again...

I think this is due to function:
>> IsInProgress(objScheduleItem)
as seen in sourcefile:
DotNetNuke_04.06.00_Source\Library\Providers\SchedulingProviders\DNNScheduler\Scheduler.vb

 Thank you for your reply but I prefer to seek answers to my questions, looking for the root of the problem will make dnn software better. (or at least increase my understanding of dnn...)

But thank you for your suggestion to work around the problem.

But I am curious, why did you configure the scheduler to run "by request" ? and why did you do a seperate check to see if the job had already run?  Did you also run into problems of items running more than you bargained for?

Thank you for your reply. it seems your troubles are the same as mine.  You must have made a name for yourself on sending that many emails !!!!

If changing the host settings to Request Method "solves" your problem then this could be because the next request is not while the schedule item is running....  And thus it will be a matter of time before a request is made at the right time and the problem can again re-occur.