Bug #3760
closed
New event has wrong next execution time
100%
Description
When adding a new recurring event in the BE module, the next execution date/time is not calculated properly. It always takes the given start date/time, which is not correct.
This does not happen when an existing event is updated: in this case a correct next execution date/time is calculated.
Other observations (for sake of completeness):
- when an event is run by the shell script, its next execution date is update properly
- when an event is executed manually from the BE module, the next execution date is not updated, which is correct, since this manual execution is "outside" schedule
Updated by Francois Suter over 15 years ago
Update: when an event is executed manually from the BE, the next execution date is:
- updated if the event was overdue, i.e. its execution date was in the past
- not updated if the execution date is in the future
This behavior is totally correct.
Updated by Francois Suter over 15 years ago
- Status changed from New to Resolved
- Assignee set to Francois Suter
- % Done changed from 0 to 100
The error happened because the start date/time of a new event was set to 1 hour in the future by default (my fault, actually). When the time is in the future, the Scheduler takes it as the start date, no matter what frequency or cron command was defined.
I set back the default time to current time and it works.
Updated by Francois Suter over 12 years ago
- Status changed from Resolved to Closed
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler