Guides
Common Magento Maintenance Problems
Magento is powerful but unforgiving. These are the maintenance problems that most often slow, break or expose Magento 2 and Adobe Commerce stores.
- Published
- Updated
- Reading time
- 7 min read
Magento – now Magento Open Source and its commercial sibling Adobe Commerce – powers some of the most complex online stores in operation. It handles large catalogues, multiple store views, B2B pricing and sophisticated promotions. That capability comes with a cost: Magento has many moving parts, and each needs regular attention to keep the store fast, secure and stable.
Most Magento problems we are asked to fix are not exotic. They are the predictable result of skipped patches, a cron job that quietly stopped running, a search service nobody was monitoring or an extension that was installed years ago and never revisited. Individually they are manageable. Together they produce the familiar symptoms: slow category pages, prices that do not update, orders stuck in processing and upgrade projects that keep getting postponed.
This guide covers the maintenance problems we see most often, why they happen and what a sustainable fix looks like.
Still running Magento 1
Magento 1 reached end of life in June 2020. Since then it has received no official security patches from Adobe. Some community projects continue to maintain forks, but a store still running unmodified Magento 1 is running software with known, unpatched vulnerabilities, often on old PHP versions that are themselves past end of life.
If you are in this position, the conversation is about migration rather than maintenance: to Magento 2 / Adobe Commerce, or to another platform that better suits your current needs. In the meantime, compensating controls – a well-configured web application firewall, strict admin access, file integrity monitoring and close review of checkout scripts – help reduce exposure but do not remove it.
Falling behind on security patches
Adobe publishes regular security updates for Magento Open Source and Adobe Commerce, along with release notes describing the issues addressed. Stores fall behind for understandable reasons: updates involve Composer dependency changes, extensions may not be compatible straight away and testing a large store takes time.
The risk is that Magento stores are high-value targets. Card-skimming attacks, admin takeovers and remote code execution vulnerabilities have all affected unpatched installations over the years.
A sustainable approach:
- Track each release line your store is on and its support period.
- Apply security-only patches promptly, using Adobe's isolated patches or quality patches where a full version upgrade is not yet feasible.
- Maintain a staging environment that mirrors production closely enough to make testing meaningful.
- Keep a written record of applied patches so you always know your actual patch level.
Our security patch management service applies this discipline across platforms, not just Magento.
Indexers that are stale or stuck
Magento uses indexers to transform catalogue, price, stock and URL data into structures the storefront can read quickly. When indexers fall behind, customers see wrong prices, products missing from categories or stock that does not match reality.
Common causes include:
- Indexers set to "Update on Save" on large catalogues, so each admin save triggers heavy reindexing.
- Indexers set to "Update by Schedule" but with cron not running, so the change log tables grow and nothing is processed.
- Indexers left in a locked or "processing" state after a failed run.
- Third-party extensions adding custom indexers that do not scale.
For most production stores, "Update by Schedule" with healthy cron is the appropriate mode. Monitoring should alert when an indexer is marked invalid or when change log backlogs grow unexpectedly, rather than waiting for a customer to notice a wrong price.
Cron is not running reliably
Cron is the heartbeat of Magento. It processes scheduled indexing, sends queued emails, cleans up quotes, generates sitemaps, runs currency rate updates and handles many extension tasks. When cron stops – after a server migration, a PHP upgrade or a change in user permissions – the store often keeps working on the surface while background work silently stacks up.
Signs that cron has a problem include order confirmation emails arriving late or not at all, the cron_schedule table growing very large, jobs showing as "missed" and indexers falling behind. Checks we routinely build in:
- Confirm the system crontab entry exists for the correct user and PHP binary.
- Monitor the age of the most recent successful cron run and alert if it exceeds a threshold.
- Review the history cleanup settings so the schedule table does not grow without limit.
- Investigate long-running jobs that block others in the same group.
Search engine problems: OpenSearch and Elasticsearch
Magento 2.4 requires a dedicated search engine for catalogue search. Older 2.4 releases used Elasticsearch; current releases support OpenSearch, and Adobe has been moving support in that direction. That means the search service is a separate component with its own version support, memory requirements and failure modes.
Typical problems include:
- Version drift – a Magento upgrade requires a newer search engine version than the server provides.
- Memory pressure – JVM heap settings that are too small for the catalogue, causing slow queries or crashes.
- Disk watermarks – when disk usage passes certain thresholds, the search engine can make indices read-only, and catalogue reindexing fails.
- No monitoring – the search service is down and the first sign is customers reporting empty search results.
Treat the search engine as a first-class part of the stack: monitor its health, plan its upgrades alongside Magento's and keep it on a supported version.
Caching misconfiguration
Magento's performance depends heavily on caching. In production that normally means full page cache served by Varnish, Redis (or a compatible store) for the application cache and sessions, and correctly configured cache invalidation.
| Problem | Typical symptom | Usual fix |
|---|---|---|
| Full page cache using the built-in file backend on a busy store | Slow uncached pages, high server load | Configure Varnish with Magento's generated VCL |
| Caches disabled "temporarily" and never re-enabled | Every page slow, admin warnings | Re-enable, then fix the original issue properly |
| Sessions stored on disk across multiple web nodes | Customers logged out, baskets emptied | Move sessions to Redis |
| Over-frequent full cache flushes by staff or extensions | Periodic slowdowns after saves or imports | Use targeted cache invalidation; review extension behaviour |
| Hole-punching gone wrong in custom blocks | Personalised data cached and shown to other users | Mark private content correctly and test |
Production mode matters too. Running a live store in developer or default mode, or failing to deploy static content correctly, has a significant performance cost. Our website speed optimisation work frequently starts with these fundamentals.
Extension sprawl and conflicts
Magento's extension ecosystem is extensive, and stores accumulate modules over time: payment methods, shipping integrations, ERP connectors, search tools, marketing pixels and bespoke customisations. Problems arise when:
- Several extensions rewrite or plug into the same core classes and conflict.
- An extension vendor stops supporting the module, blocking upgrades.
- Modules are installed by copying files into app/code rather than through Composer, making versions hard to track.
- Disabled modules are left in the codebase, still adding to compilation and complexity.
A periodic extension audit – listing each module, its purpose, owner, version, compatibility and whether it is still needed – is one of the most valuable maintenance exercises for a mature Magento store.
Upgrades that keep getting postponed
Because each Magento upgrade can involve PHP, MySQL or MariaDB, the search engine, Composer packages and extensions, upgrades are often deferred until the store is several versions behind. The longer that goes on, the bigger and riskier the eventual project becomes – and the closer you get to running on unsupported versions.
Breaking upgrades into a regular cadence keeps each step smaller. A practical upgrade process includes a dependency review, a fresh staging environment, automated or scripted regression tests for key journeys, a rehearsal deployment with timings, and a rollback plan using verified backups.
Infrastructure and database drift
Finally, Magento is sensitive to its environment. Database tables that grow without cleanup (logs, quotes, report data), missing indexes on custom tables, PHP settings copied from a different application and servers that have not been patched all contribute to gradual degradation. Regular database maintenance and server patching are part of keeping Magento healthy, not separate concerns.
Bringing it together
None of these problems is unusual, and none is a reason to abandon Magento. They are a reminder that Magento needs a maintenance routine that covers the application, its supporting services and the infrastructure underneath. Our Magento maintenance service is built around exactly that: patching, cron and indexer monitoring, search and cache health, extension reviews and planned upgrades.
If your store is showing any of the symptoms above, a technical audit is a sensible first step. It gives you a clear picture of patch level, configuration and risk before you commit to a larger project.