Magento cron health can make or break stock availability
When stock indexing runs on schedule, unhealthy cron delays what customers see. How to monitor cron and mview queues before problems reach the storefront.
When stock indexing runs on schedule, unhealthy cron delays what customers see. How to monitor cron and mview queues before problems reach the storefront.
Once stock indexing moved to scheduled processing, cron and the mview queue became critical — any delay in cron directly delayed stock visibility for shoppers.
Why cron matters
Cron runs indexing, emails, order processing and integrations. If it stops or falls behind, stock changes queue up and the storefront shows outdated information.
RELATED GUIDEGoogle Merchant Center feed optimisation: fix disapprovals and win more Shopping clicks → Need reliable ecommerce support?Patches, upgrades and fixes from certified developers.Get a free store health check →What to monitor
- Last successful run of key cron groups
- Failed and missed jobs in cron_schedule
- Mview changelog backlog size
- Indexer status (valid / invalid)
- Long-running or overlapping jobs
Common mistakes to avoid
How we help with ecommerce
Frequently asked questions
How often should Magento cron run?
Typically every minute.
Can cron slow the site?
Heavy jobs can — separate or schedule them carefully.
Do you monitor cron for clients?
Yes, as part of ecommerce support and VISIBI Guard.