Even with lots of timing options, it wasn't that hard. I had a schedule record and just went through each schedule and executed jobs associated with the schedule during an interval when a schedule was triggered. Name StartTime EndTime RepeatIntervalMinutes DaysOfWeek DaysOfMonth Hours Minutes NextRunTime LastRunTime friday7 2014-09-05 00:00:00 2020-04-18 00:00:00 90 Friday NULL 7 NULL NULL 2015-03-13 07:00:49.9115390 -05:00

I used to think that I wanted a job scheduler to do things, but I thought all the .NET ones were over-complicated. So, I spent a couple hours or so and wrote one in to my app. Just have a timer that checks your configured jobs every interval (maybe a minute or less) if it's time to run one, then run it. There's a few other complexities to deal with, but it's not as hard as you think. Think about the configuration for Unix chron as the simplest way do it with lots of timing options.