How to tell if Magento cron has stopped
A practical check you or your developer can run in five minutes, and what each answer means.
Magento does a lot of its work in background jobs that run through cron: reindexing, sending order emails, updating prices and stock, cleaning up quotes, processing queues. When cron stops, nothing looks broken at first. Then search results go stale, emails stop, and stock goes wrong.
Here is how to check, from the simplest test to the most detailed.
1. Is the cron line installed?
On the server, as the user that runs Magento:
crontab -l
You should see a line that runs bin/magento cron:run every minute, usually marked with #~ MAGENTO START and #~ MAGENTO END. If it is missing, cron is not running at all. Magento can install it with bin/magento cron:install.
On Adobe Commerce Cloud, cron is managed in .magento.app.yaml, so check the crons section there instead.
2. Are jobs actually running?
Magento records every scheduled job in the cron_schedule table. Ask your developer to look at the latest rows:
SELECT job_code, status, scheduled_at, executed_at, finished_at
FROM cron_schedule
ORDER BY scheduled_at DESC
LIMIT 20;
What the answers mean:
- Recent rows with status
success: cron is running. - Only
pendingrows, and nothing executed recently: the cron line is there but jobs are not being picked up. Check that the server's cron service is running and that the PHP path in the cron line is correct. - Many
missedrows: jobs are being scheduled but starting too late, often because a long-running job holds things up. errorrows: jobs start and fail. Themessagescolumn says why.- A
runningrow that is hours old: a job is stuck, and other jobs in its group may be waiting behind it.
3. What do the logs say?
Look at var/log/cron.log and var/log/exception.log for errors around the time things stopped.
Keep an eye on it automatically
Checking by hand works once. The StoreOnCall plugin reports through Magento's cron every 5 minutes, so if its reports stop for 20 minutes, cron has almost certainly stopped, and you get an alert. It also watches failed, missed and stuck jobs. See Background jobs (cron) running for the exact rule.