Is your checkout working right now? Find out in a few minutes, free, no sign-up.Scan my store

Blog

The first hour after a Magento deployment: a checklist

Most store problems start with a change. Ten minutes of checks right after a release catch the expensive ones.

Deployments, extension updates and setting changes are the most common starting point for a broken store. The fix is usually easy if you notice within the hour, and expensive if a customer tells you the next morning.

Here is a short checklist to run after every release.

Straight after the release

  1. Buy something. On your phone, in a private window: open a product, add it to the cart, go through checkout to the payment step. Try at least one product with options.
  2. Check every payment method appears. A payment module that failed to compile or lost its credentials often just disappears from the list.
  3. Check the logs. Look at var/log/exception.log and var/log/system.log for new errors since the release.
  4. Check the indexes. Run bin/magento indexer:status and look for anything that is not "Ready".
  5. Check maintenance mode is off. bin/magento maintenance:status. It happens more often than anyone admits.

Within the hour

  1. Confirm cron is still running. A deployment that changes paths or PHP versions can break the cron line. See how to tell if Magento cron has stopped.
  2. Check an order email arrives. Place a real order with a test payment method if you have one, or watch the next real order.
  3. Check caches. If you see old content, flush the cache that is out of date rather than all of them.
  4. Watch orders against normal. If orders slow down compared with the same hour last week, look before you assume it is a quiet day.

Make the next release calmer

  • Keep a short record of what changed and when, so "what changed?" has an answer.
  • Plan releases outside your busiest hours.
  • If you use StoreOnCall, set a planned-work window so the release itself does not set off alerts, then let the checkout test and the order checks watch the hours after. Each alert names recent deployments and extension changes as a likely cause.

You can see the checks behind this list on what we check.

WhatsApp us