Work that runs on a timetable.
WHAT THE FRAMEWORK PROVIDES
A scheduler defined in code, listing what runs and when.
HOW IT WORKS
A single cron entry runs the scheduler every minute.
The scheduler decides what is due.
WHY THAT DESIGN
All scheduling lives in code, versioned and visible, rather than scattered in cron.
WHAT TO SCHEDULE
Cleanup Report generation Data synchronisation Queue processing, where no persistent worker exists
WHAT TO CONFIGURE
Prevention of overlapping runs Output handling Failure notification
THE OVERLAP POINT
A task taking longer than its interval will otherwise run alongside itself.
WHAT TO SET ON CPANEL
One cron entry, with the full path to PHP and to the scheduler command.
WHAT TO CHECK
That the cron entry uses the correct PHP version That output is captured
WHAT TO MONITOR
That tasks actually ran.
WHAT TO AVOID
Long-running tasks inside the scheduler, which block subsequent runs.
