The system's scheduled tasks were functions called from a single entry point, with nowhere to see what ran, when and with what result. This delivery creates the task registry and the panel to follow them.
How it works
A module declares the task and its frequency. The server's scheduler calls the system at regular intervals, and the system runs the tasks of that frequency. When done, each one records status, duration and log.
The panel
- List of tasks, by module and frequency.
- Result of the last run, with the log.
- Pause and resume a task.
- Run now, without waiting for the next slot.
Tasks written in the previous format keep working.
Stated limits
- The server's scheduler has to be configured: the system does not schedule itself.
- A task runs at the interval's frequency; individual times and expressions are not evaluated yet.
- There is no lock against the same task running twice at once.
Source: Core · commit a5976ba9 · Admin Cron