Skip to content
Log inStart free

Handling System Errors

You hit an error message in the admin or a customer hits one on the storefront, and you need a calm way to handle it. This walks the quick checks that clear most errors, how to tell a passing glitch from a real problem, and what to gather before you contact support.

Updated
Reading time
4 min
On this page

When an error appears, whether in your admin or on your storefront, most of the time it is a passing glitch that a couple of quick checks will clear, and only occasionally a real problem that needs reporting. Handling it calmly means working through the simple checks first, then deciding whether the error is affecting only you or everyone, and finally gathering the details that let support help you quickly if it turns out to be genuine. This article gives you that order to follow, and points to the specific guides for the common problems that have their own fix.

First, the quick checks

Most errors clear with one of these, so try them before assuming something is broken.

  • Reload the page, since a single failed request often succeeds on the second try.
  • Open the same page in a private browser window, which rules out a stale cached version or a browser extension interfering.
  • Check your internet connection, because a dropped or unstable connection shows up as an error that has nothing to do with the store.
  • Wait a moment and retry, since a brief hiccup on any online service resolves itself given a few seconds.

Before you begin

  • Any role can report an error; what you can change afterwards depends on your access.
  • You can note the exact wording of the error and what you were doing when it appeared.
  • Open the page in the admin where the error appeared, or have the details of the error a customer reported to hand.

Steps

1. Note exactly what happened

Write down the exact error message, the page you were on, and what you were doing when it appeared. A precise record is what lets you or support reproduce and fix the problem, rather than searching blindly.

2. Run the quick checks

Reload the page, then try it in a private browser window, and confirm your connection is stable. Most errors are cleared by one of these, so running them first saves you from reporting a problem that was never really there.

3. Decide if it is just you or everyone

Try the same action from another device or connection, or ask a colleague to try it. If it works elsewhere, the problem is local to your browser or connection. If it fails for everyone, it is more likely a real issue worth reporting.

4. Check whether it is a known problem

Some errors have a specific cause and a fix of their own, and following that guide is faster than treating the error as a general fault. Match what you are seeing to one of these:

5. Gather details and contact support

If the error persists and affects real work, contact support with what you recorded: the exact message, the page, the steps that reproduce it, and whether it happens on other devices. Giving these upfront means support can help on the first reply instead of asking for them.

Tip: Record the exact message before you do anything else. Once a page reloads, the wording is often gone, and that exact text is the single most useful thing for finding the cause or getting help quickly.

Verify the result

  • The action that failed now completes after the quick checks, or you can reproduce the error deliberately.
  • You know whether the problem affects only your browser or everyone.
  • If you reported it, you gave support the exact message and steps to reproduce it.

Best practices

  • Capture the exact error text and a screenshot before reloading, since the wording is the most useful detail for a fix.
  • Try a private browser window early, which clears a large share of errors caused by cache or extensions.
  • Confirm whether the problem is local before reporting it, so you do not raise an issue that is only on your device.
  • Follow the specific guide for a known problem, rather than treating a payment or delivery issue as a general error.

Next steps

Still stuck?

We use cookies

Necessary cookies keep the site working. With your permission we also use analytics and marketing cookies. Change your choice any time in Cookie settings.