There is just one single cronjob needed which takes care of all implemented cronjobs. It automatically resumes cronjobs (eg. when the server was down for a short time), therefore increases stability and keeps the whole cronjob administration in the database.

Setup / configuration

The only cronjob you need is one that calls the URL every 10 minutes. If you use smaller intervals (eg. 1 min) the not_before_time defined in your cronjob config is executed more precisely.

The cronjobs are configured directly in the database table fcs_cronjobs. There is no backend so far.

Important information

Backwards compatibility

The cronjobs that you set up before migrating to v2.3 still work and will work in future, but the new system is recommended.