Project

General

Profile

Actions

Bug #25674

closed

Calculation of next execution time wrong for configured start time in future

Added by Marcus Krause over 13 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
scheduler
Target version:
-
Start date:
2010-11-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #25677: tx_scheduler_CronCmd needs refactoringClosedChristian Kuhn2010-11-29

Actions
Actions

Also available in: Atom PDF