Manually starting a Scheduled Task should not update the next run

Manually starting a Scheduled Task should not update the next run date

Arild Henrichsen

Vote:

When starting a Scheduled Task manually, the next run date is automatically set to (now + specified interval).

Let's say there's a heavy job that syncs a whole bunch of data, which is set to run during the night. The job has gone FUBAR for some reason, so the admin runs the job manually during daytime to get the data up on the site. The next run date is now daytime the next day, which the admin may not notice.

Manually starting a Scheduled Task should not update the next run date.

#140391

Oct 19, 2015 10:04

Jonas Klingsdal

Vote:

Hi Arild

I took the liberty to report this as a bug

/Jonas

#140402

Oct 19, 2015 13:05

Arild Henrichsen

Vote:

Thanks Jonas. I figured this was by design, which is why I filed it as a request instead of a bug.

#140403

Oct 19, 2015 13:08

Jonas Klingsdal

Vote:

I understand. Talked it over with the team, and noone had a good argument for why it is that way.

#140410

Oct 19, 2015 13:57

Per Bjurström

Vote:

This have now been fixed so that next execution date is always calculated based on the previous execution date (rather than when it was manually started). Should show up in a release the coming weeks.

#171969

Nov 22, 2016 15:44

Arild Henrichsen

Vote:

Excellent, thanks Per!

#171971

Nov 22, 2016 15:47

Arild Henrichsen

Vote:

For the record, the fix was introduced in Episerver.CMS.Core 10.3.0.

#173701

Edited, Jan 05, 2017 13:42

Try our conversational search powered by Generative AI!

Manually starting a Scheduled Task should not update the next run date