Tools for the people who run a Magento 2 store day to day: see and control cron jobs, and see who changed what in the admin.
Cron job manager for Magento 2: list, run, enable, disable and reschedule cron jobs, see the schedule grid and timeline, and get health warnings and failure emails when cron is not running.
$99
Admin activity log and audit trail for Magento 2: field-level change history, admin login history, active session control, security notifications and an admin IP allowlist.
$139
Magento relies on cron for emails, indexes, price rules and much more, but has no admin screen to see or control it. Cron Manager lists every cron job with its schedule, last run, status and average duration. You can run a job now, enable or disable it and change its schedule without editing code, see the cron_schedule table as a grid and as a timeline, and clean up the queue. It warns you when cron stops running or a job keeps failing, and can send failure emails.
Our posts explain how to tell when cron has stopped and how to pause or reschedule one cron job.
Magento Open Source records when a product was last updated, but not who changed it or what the old value was. Admin Activity Log keeps an admin action log with old and new values field by field for products, categories, CMS pages, customers, orders, price rules, configuration, admin users and roles. Mass actions, imports and config:set from the command line are logged too.
The login history shows successful and failed sign-ins, the active sessions list shows who is signed in now and lets you end a session, and you can get security notifications and limit the admin to an IP allowlist. Passwords, keys and other secrets are masked in the log. See who changed this price?
Cron Manager works with Magento's own cron, so the server crontab still has to be set up; the module shows you when it is not running. The activity log records changes made in the admin and through config:set, so changes made straight in the database are outside its view.
Yes. Cron Manager can disable one job or give it a new schedule from the admin. The change is stored in the configuration, so it can be exported with app:config:dump, and the job can still be run by hand.
No. Passwords, tokens, keys and other sensitive configuration values are stored masked. You can still see that they were changed and by whom.
Yes. Magento's cron still has to run from the server crontab. Cron Manager shows and controls the jobs and warns you when cron has stopped.
From the blog
Magento Open Source records when a product was last updated, but not who changed it or what the old value was. Here is how to trace a price change and what an admin activity log adds.
Magento has no switch to pause a cron job and only a few jobs have a schedule setting. Here is what you can do with configuration, what needs code, and how to do it from the admin.
When order emails, indexes or price rules quietly stop updating, cron is often the cause. Here is how to confirm it from the cron_schedule table and what to check next.
We use necessary cookies to run this site and, with your permission, Google Analytics to understand how it is used. You can accept analytics, reject it or choose in the settings. Cookie policy
Choose which cookies you allow. Necessary cookies are always on because the shop cannot work without them. You can change your choice at any time with the "Cookie settings" link.
Needed for the basket, checkout, login and security. They do not track you.
Google Analytics: how many people visit, which pages they read and how they found the site. It sets the _ga cookies and sends usage data to Google.
