It was always my understanding that the start time applied to every iteration of the task (i.e. if hourly and start time of 11a, it would run from 11a to the end time time (or the end of the day, if no end time was specified) every day. If weekly task and start time of 11a, it would run once a week at 11a). I just confirmed this in the logs for our CF7 servers, and our hourly tasks that are scheduled to run from 11a-4p run at 11, 12, 1, 2, 3, and 4. Is it possible that the start time for the task was changed at some point?

So this would mean that your task would only execute if the 'HOUR' was currently 3 right - (greater than or equal to 3 and less than 4).

So your Scheduler is set to 'hourly', then this should only execute on the 3rd hour - assuming 1x a day then right? (as a time of 3 pm returns 15 as the hour)

So yes, I could see, setting up a Scheduler for 11 am would not work - even though, the next day - hourly, a person would think that the task would roll to the next hour in the morning etc.

The key here is to look at the scheduler log - and look for the 'Rescheduling for' value - as when a scheduled event ends - it should setup the next schedule for you. (make sure you log scheduled tasks etc - cfadmin Debugging and Settings - Logging Settings Enable logging for scheduled tasks)

I'm currently in a thread on the yahoo 'coldferusion' group about a scheduled task issue I'm seeing and is repeatable regarding long running threads, if interested http://tech.groups.yahoo.com/group/colderfusion.