Bug #25674
closedCalculation of next execution time wrong for configured start time in future
0%
Description
When creating a recurring task, setting a start date and frequency (seconds or cron command) is mandatory.
If you provide a cron command as frequency and start time is set in future, the calculation of "next execution" is wrong - meaning "next execution" is always the start date not considering the cron command frequency.
If the start date is set to a time in the past or now (=leaving field value untouched), the "next execution" is correctly calculated based on the cron command.
Use cron command "0 3 1 1,4,7,10 *" (execution on first day of January, April, July, October) and set the start date to a date in future (e.g. tomorrow).
Then "next execution" is tomorrow (and actually task run) not considering cron command.
(issue imported from #M16329)
Updated by Christian Kuhn almost 14 years ago
This is solved with #16611 in 4.5, is it?!
Updated by Francois Suter almost 14 years ago
Marcus, any feedback? According to my tests, this now works fine in trunk.
Is that enough for you if this is fixed only in upcoming 4.5? If not, please consider providing a patch for older versions.
Updated by Francois Suter almost 14 years ago
Markus, ping!
This is resolved as far as I'm concerned.
Updated by Marcus Krause almost 14 years ago
got me, I was quite busy these days
no longer reproducable with #16611!
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler