Magento 2 Cron Monitor: Monitor Cron Jobs with Failure Alerts
SKU: CRONMONITOR1
- Overview of all cron jobs with status, duration and next run
- Email alerts on failure, debounced against mail floods
- Detect stuck jobs and total standstill, even when nothing runs at all
- Schedule jobs manually, with its own permission
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 cron monitor: watch cron jobs before customers notice
Indexers, newsletters, sitemaps, price rules: without a running cron a lot stands still. The module makes that visible before customers notice.
A Magento 2 cron monitor shows in the admin what happens in the background of your shop: which cron jobs ran, which failed, which are stuck. This page is about a Magento 2 cron extension that makes Magento's cron_schedule table readable, warns by email on failures and queues single jobs for the next run.
The extension is set up in your shop by Mironsoft after purchase. It is a pure admin module with no effect on the frontend, so no consequences for Hyvä, load time or the full page cache. If the Magento cron is not running in your shop and nobody notices right away, that is exactly the gap the Magento 2 cron monitor closes.
Central job overview
Last run, duration, status and next run per job in one filterable grid.
Email alert on failure
On status error the module notifies your recipient list, with the error message in the text.
Detect stuck jobs
Jobs that stay in status running longer than your limit are flagged and reported.
Standstill watchdog
If no cron runs at all any more, the heartbeat check raises the alarm.
Schedule manually
Single jobs can be queued for the next cron run, protected by ACL.
History and cleanup
Run times per job over time; old entries are removed after the period you set.
Magento 2 cron monitor: all cron jobs in one grid instead of a database peek
Magento writes every scheduled run into the cron_schedule table, but the admin shows none of it. The module prepares the data: per job code you see the last successful run, the duration, the number of errors and missed runs and the next scheduled time. Filters by cron group (default, index, …) and status reveal anomalies at once.
Especially in shops with many modules dozens of jobs pile up: indexers, newsletters, sitemap generation, price rules, cart reminders. The Magento 2 cron monitor groups them by cron group so you can check only the index group, for example. Unusual run times show in the history before a job actually fails.
- Columns: job code, group, last run, duration, status, next run
- Filter by group, status and period, CSV export
- Coloured status marks for success, error, missed and running
Magento 2 cron failure alert without a mail flood
You decide which states trigger an email to your recipient list: on error, on too many missed runs, or on jobs running longer than your limit. So a broken job does not fire a mail every five minutes, an adjustable lock period applies per job. The mail names the job code, the time and the stored error message. A test mail checks the delivery path beforehand.
The difference between "error" and "missed" is practical: a missed run usually means the cron was overloaded or briefly stopped. Repeated errors point to a code or data problem. The Magento 2 cron monitor evaluation separates both cases so you do not need to react to every single hiccup.
- Triggers selectable individually: error, missed, runtime limit
- Lock period per job against mail floods, e.g. one mail per hour
- Any number of recipients, test mail at the push of a button
Detect standstill and stuck cron jobs in Magento
The most dangerous outage is a silent one: the system cron has stopped, so nobody writes an error either. The module checks the time of the last executed job. If it is further back than your tolerance, the heartbeat check raises a warning. It also marks jobs that have been in status running beyond your limit as stuck, so blocked runs do not unnoticed hold up other jobs.
This includes the time between the end of the last job and the expected start of the next. If the cron fails after a server update or a changed crontab line, the Magento 2 cron monitor tells you within your tolerance, not only when customers get no order confirmation.
- Tolerance in minutes freely adjustable
- Stuck running jobs are flagged separately
- Admin dashboard notice as soon as the heartbeat is missing
Run a Magento 2 cron job manually: queue it instead of using SSH
Instead of searching for the right command via SSH, you select a job in the grid and schedule it. It then runs in the next regular cron pass, under the same conditions as in normal operation. Scheduling has its own ACL resource so that not every admin user can trigger jobs; every action is recorded with user and time in the history.
Jobs are only queued, deliberately not executed directly. That way the job behaves as in normal operation, with the same rights and the same environment. You can restrict scheduling to single admin roles so the Magento 2 cron admin module separates permissions cleanly.
- Own permission, separate from plain viewing and configuration
- Log: who scheduled which job and when
- Not a replacement for server-level monitoring, but an addition in the admin
What a Magento 2 cron monitor is needed for in daily work
These typical situations show when a look at the cron jobs makes the difference.
Check after a deployment
After updates or module installations the Magento 2 cron monitor shows whether all jobs run on schedule again and new jobs start without errors.
Protect newsletters and cart mails
If newsletter_send_all hangs, no mails go out. The alert reports it before customers ask.
Agencies with several shops
If you look after many installations, the Magento 2 cron monitor saves the search via SSH. Support sees the status without being allowed to trigger jobs.
Watch imports and indexers
Long run times of indexers or ERP imports stand out in the history before the limit is exceeded.
Monitor Magento cron: without a module and with a Magento 2 cron monitor
This is how daily work differs with and without the extension.
| Topic | Without a module | With Mironsoft Cron Monitor |
|---|---|---|
| Overview | Querying cron_schedule via SQL | Admin grid with filters, status and run time |
| Noticing failures | By chance or through a customer call | Email alert to your recipient list |
| Stuck jobs | Unnoticed, blocking following jobs | Limit in minutes, flag and notification |
| Cron standstill | Noticed days later | Heartbeat check with adjustable tolerance |
| Triggering a job | SSH access and the right command | Schedule with one click, own ACL permission |
| Traceability | No history | History with user and time, automatic cleanup |
How we set up the cron monitor after your purchase
This is how you get from purchase to a working alert.
Order and review
After payment we get in touch within 2 working days and clarify how your cron is set up and which jobs are critical.
Installation in your shop
We install the Magento 2 cron monitor, assign the ACL resources and test the display with your real jobs.
Define limits
We agree the runtime limit, heartbeat tolerance and lock period with you.
Test the alert
A test mail checks the delivery path, then we trigger a controlled alert together.
Handover
You get a short briefing on which role may see and schedule what.
Cron monitor or email log? Delimitation from related modules
The Magento 2 cron monitor watches jobs, not emails. If you want to know whether and when a message was sent, you need an email log with resend; that is a separate module. They complement each other: a failed newsletter job in the cron monitor and the missing mail in the email log show the same problem from two directions.
Mironsoft's Cache Warmer also runs as a cron job. It appears in the monitor like any other job and benefits from its alerts. The monitor does not replace server monitoring; it is a Magento 2 cron extension that shows in the admin what Magento itself knows about its jobs.
No download — personal setup instead
The Magento 2 cron monitor is not listed here as a ready-made download for self-installation. The purchase is a service commission: we get in touch after the purchase, set up the module and agree on the recipient list, limits and permissions together with you.
Frequently asked questions
Everything important about the Magento 2 cron monitor: alerts, limits and the purchase process.
How can I see in Magento 2 whether the cron jobs are running?
Does this replace server monitoring?
Will I get constant mails for a broken job?
Does manual scheduling start the job immediately?
How is a standstill of the whole cron detected?
Does the module make the database grow?
Who may see or do what in the admin?
What should I do if the Magento cron is not running?
How do I start a cron job manually in Magento 2?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 cron monitor – Mironsoft