Skip to content

Cron Manager

Magento’s cron is usually a black box you can only inspect over SSH. Cron Manager brings it into the admin: a grid of every configured job, a colour-coded timeline of recent runs, run-now buttons for a single job or the whole queue, schedule management, and email alerts when a job fails — so you can see what cron is doing and fix it without leaving Magento.

Cron Jobs configuration grid

Magento

Open Source 2.4.9 GA (and later 2.4.x).

PHP

Tested on 8.4 and 8.5.

No SSH

Inspect, run and diagnose cron entirely from the admin.

Alerts

Optional email on job failure.

Every configured cron job — code, group, the class/method it runs, its schedule and status — with Last Cron Activity so you can tell at a glance whether cron is even running.

Cron Tasks timeline

  1. Run a single job — click its action in the Jobs grid to execute it immediately and see the result.

  2. Run the whole queueRun Cron triggers a full cron pass on demand (handy after a fix, or on a host where the system crontab isn’t firing).

  3. Mass-execute selected pending schedule entries, or mass-delete stale ones.

Turn on email notifications and Cron Manager emails you when a job errors — so a silently failing reindex, feed export or order-sync surfaces as an alert instead of a mystery days later.

How do I know if cron is actually running?

The Jobs grid shows Last Cron Activity and the timeline shows recent runs colour-coded by outcome. If that timestamp is stale or the timeline is empty, your system cron isn’t firing — and you can trigger a pass with Run Cron while you fix it.

Can I re-run a job that failed without waiting for its schedule?

Yes — run it immediately from the Jobs grid, or mass-execute pending schedule entries. The result (success or the error message) is shown right away.

Will the schedule table grow forever?

You can mass-delete old cron_schedule rows from the Schedule grid to keep it lean, filtering by status first to target exactly what you want to clear.

Is running jobs from the admin safe?

Yes — only jobs registered in Magento’s cron config can be run (looked up by code, not by an arbitrary class name), every action is behind the Cron Manager ACL resource, and bulk operations are POST-protected. Verified clean on PHP 8.4 and 8.5.