Let's try refreshing the job's settings. After applying the update, adjust your job's start date/time to something else and then save it. Then edit the job again and put back your original start/date time.
Thanks for the quick reply! We are running the most recent version - the release notes state the problem we are experiencing was fixed, but it appears to not be fixed.
We performed a clean install when we originally set this up - no upgrades or anything like that.
I went ahead and changed the start date on both jobs to 3.19.2014, where DST is 'on' - we'll see if that helps.