Bug #4224
closed
Scheduled tasks are not all executed by the cron script
Added by Francois Suter over 15 years ago.
Updated almost 11 years ago.
Description
I currently have a situation where my scheduled tasks are ignored by the cron script. I think it's because there's a single task with no next execution date at the top of the tasks list.
I have no time to investigate now, so I'm opening this bug report not to forget.
- Status changed from New to Needs Feedback
- Assignee set to Francois Suter
- Priority changed from Must have to Should have
I haven't been able to reproduce this situation. I'm leaving this bug report open for feedback in case someone stumbles on a similar case again.
- Status changed from Needs Feedback to Resolved
- % Done changed from 0 to 100
I think I have solved this in r1123.
The error was in tx_scheduler::fetchTask() in the SQL WHERE clause to get the next task to execute:
$whereClause = 'disable = 0 AND nextexecution != 0 AND nextexecution < ' . $GLOBALS['EXEC_TIME'];
This would not take tasks whose next execution time is equal to $GLOBALS['EXEC_TIME'], which is wrong since they are definitely ok to run.
I simple changed the nextexecution test to "<=".
- Status changed from Resolved to Closed
- Category set to scheduler
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
Also available in: Atom
PDF
Updated by 
Updated by