I'm currently running DNN version 3.2.2, and have a scheuled event that send out an email to users that are about to expire. The problem is, when I was testing, when changing the schedule, the updates I made didn't always take. They saved, and when I looked at the details in the "edit schedule" screen, it's all as I set it, however, the settings don't take. Example, I had it set to run hourly, but for testing purposes, I wanted it to run every minute for a bit. The next minute, it sent, but then it scheduled the next event for an hour later. I went back in to edit the schedule again (and the settings were all fine), saved, and again, it sent a minute later, but again, it set it for an hour later.

The next issue I had was, when running it in a multi-server environment, even though it was only set to run on one server, I would get two messages within a few seconds of eachother. When looking at the logs, I could see that, in fact, it was only running on web01, as specified, but firing it off twice, within a few seconds of the first firing, and stranger still, the event takes anywhere between 10 and 45 seconds. It had an object dependency, so I would have thought that it would not be able to fire off while it was already running anyways.

Finally, I disabled the task, on Friday. It continued to run, however, for about a day and a half before stopping.

Anybody else have similar issues with this kind of bug?