Cron Manager: setup and help

In your Back Office, open Modules > Module Manager, choose Upload a module, and upload the module ZIP. Install it, then click Configure. On older PrestaShop versions, use the corresponding Modules page.

Open Cron Manager > Settings > Configuration. Use Server cron (recommended) when your host supports scheduled PHP commands. Use cron-job.org or another external HTTP scheduler when you need a remote trigger. Front office fallback and Back office fallback need page visits. They do not provide a fixed execution time.

Install the MPR modules whose tasks you want to run. Open Modules in Cron Manager and sync their definitions. One central trigger dispatches due registered tasks. It does not discover arbitrary scripts as tasks.

In Cron endpoints, copy Server cron command, HTTP cron URL, or Shared cron token. The token is generated as 64 hexadecimal characters. Regenerating it invalidates your old commands and URLs. Update every scheduler after regeneration.

Server cron

The generated copy command uses --token=TOKEN, which the current runner accepts. For a server setup, you can instead put the token on the first line of a file outside the public web directory. Give only the scheduled PHP user read access, for example file mode 0400. Use absolute paths appropriate to your hosting:

* * * * * /usr/bin/php /path/to/prestashop/modules/mprcron/cron.php --token-file=/private/mprcron.token --max-tasks=20 --max-seconds=300 --context=cron

Do not copy these example paths literally. The PHP CLI executable must be able to load your shop and its dependencies. Command tasks also need the server to permit process execution.

HTTP scheduler

Copy the shop-generated HTTP cron URL. Its format is:

https://yourshop.com/module/mprcron/cron?token=YOUR_TOKEN
https://yourshop.com/module/mprcron/cron?token=YOUR_TOKEN&max_tasks=20&max_seconds=300

For cron-job.org, save your key and interval, then use the create/sync job control. Use Test public request to check reachability. You can pause, resume, delete, or disconnect the external job from this screen. Authentication walls, maintenance restrictions and firewalls can block remote requests.

Limits and context

A runner call defaults to 20 tasks and 300 seconds. The limits are clamped to 1 through 100 tasks and 10 through 300 seconds. These are invocation parameters, not configuration form fields. The CLI accepts --max-tasks, --max-seconds, and --context=cron|front|admin. The module front-controller endpoint executes in cron context. Do not expect its query string to change that context.

Use Dashboard for a summary. Tasks shows the owner module, task key, label, type, schedule, enabled state, context, priority, timeout, last run and next run. Use Run for immediate execution. Use Pause or Resume to change one task. Edit a module-defined frequency and reset it to the module default when required.

Use Modules to sync definitions, pause or resume a module's tasks, or remove registrations. Removing a module-defined registration can be reversed by syncing the owner. Removing a custom task deletes that custom definition.

Create a custom task

Your employee profile needs the corresponding task view, add, edit or delete rights for the action you use.

Open the custom task form in Tasks.

Use Test run or Save and test run and inspect the result. An HTTP scheduler or fallback page visit does not execute command tasks. The Tasks Run action uses the explicit admin test context.

Schedules

hourly:00
daily:04:00
weekly:1:08:00
weekly:1,3:08:00
every:3600
*/15 * * * *
0 3 * * *
30 2 * * 1

Weekly day 0 is Sunday and day 1 is Monday. every:3600 uses seconds. Calendar schedules use the PHP runtime timezone. Check it against the times shown in the task list.

For a supplier import, enter Name Nightly supplier import, Type URL, Method POST, Schedule daily:02:30, and the supplier's URL. Set Expected HTTP status to 200. Add Content-Type: application/json to Headers and this Body:

{"source":"prestashop","mode":"scheduled"}

For a callable use module_name::method. For a command use an absolute command such as php /path/to/script.php.

1. Use Run on one safe task. Check Logs for its status, context, duration and result preview.
2. Wait for your scheduler's next trigger. Check Hits for a server or external hit, then check the task's Last run and Next run.
3. If hits arrive without executions, check Enable cron execution, the task's enabled state, schedule and context. A task claimed by another runner is skipped.
4. If no hits arrive, check the scheduler path, token and public reachability. A manual run only tests the task itself; your hosting scheduler still has to call the URL.
5. For failed, timeout or crashed results, inspect the result and the target script. Failed runs advance their next execution with a retry delay. CLI subprocess isolation is used when available so one crashed task need not stop the batch.

Authenticated diagnostic URLs use the same endpoint:

?token=YOUR_TOKEN&action=status
?token=YOUR_TOKEN&action=health
?token=YOUR_TOKEN&action=tasks
?token=YOUR_TOKEN&action=tasks&module=mprcron
?token=YOUR_TOKEN&action=run&id_task=123

Hits distinguishes server, external, front office, Back Office, fallback and manual triggers. Logs records executions. Use Settings > Integrity for installation checks. License, Support and Update are also under Settings.

If you maintain an MPR module, use the bundled MyPrestaRocks\Cron\CronTrait, declare tasks in getCronTasks(), and call its cron installation and uninstallation methods in your module lifecycle. A task definition can contain:

'refresh_feed' => [
    'label' => 'Refresh product feed',
    'callable' => 'mymodule::cronRefreshFeed',
    'schedule' => 'daily:03:00',
    'context' => 'cron',
    'priority' => 50,
    'timeout' => 120,
]

Sync the owner in Modules after changing definitions.

Turn off Enable cron execution for a temporary stop, and check your external scheduler separately. Remove the hosting cron entry or pause/delete the external job when retiring the module. Uninstall from Module Manager. The uninstall routine unregisters Cron Manager's own tasks and removes its menu. It keeps shared cron tables because other modules can still use them.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.