> ## Documentation Index
> Fetch the complete documentation index at: https://andcze.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Errors
> A log of everything that goes wrong in your shop — check here first when payments or notifications stop working.
The **Errors** tab is the central log of everything that has gone wrong in your shop. You'll find it in the panel under **Settings** (marked with a warning icon in the sidebar). It's the first place to look when something isn't working the way it should — before you start to worry or reach out to support.
## What this tab is for
Your shop does a lot of work behind the scenes: it takes payments, fulfils orders, sends notifications to Discord, runs the AI assistant. If any of these tasks fails, the shop records it here — along with information about where and when the problem happened and exactly what went wrong.
That way you don't have to guess. Instead of asking "why didn't the customer get their rank?", you open **Errors** and see the exact reason.
Always check here when **payments** or **notifications** stop working. Most of the time you'll find a ready answer about what went wrong and what to fix.
## How the page is laid out
The page has two parts, one above the other:
A panel at the top with three dropdown lists. It narrows down the list so you can quickly find the errors you care about.
The list of entries below the filters. Each row is one recorded problem — newest at the top, oldest at the bottom.
## What kinds of errors end up here
The log gathers problems from several different areas of the shop. Each area has its own coloured **category badge**, so you can see at a glance what an entry is about:
Problems when starting a payment, receiving confirmation that money has come in, or making refunds. This is the most common category.
Errors while fulfilling an order — for example when a purchased item couldn't be delivered in-game.
Cases where an outgoing notification — most often a message to your Discord server — wasn't sent.
Problems with the assistant that helps you inside the panel.
Other technical shop errors that don't fit into the groups above.
Older entries, recorded before categories were introduced, are treated as **Payment**. That's why payment errors are often the largest group on the list.
## How to read a single entry
Each error on the list is one entry. On the top line of the entry, side by side, you'll see small badges, and beneath them the full text of the error. Together they tell you everything you need:
The coloured label at the start of the row — it immediately shows what the error is about (e.g. **Payment**, **Order**, **Webhook**, **AI Assistant**, **System**).
The bold text next to the category — it tells you where the error came from, such as the name of the payment gateway that reported it.
For payment errors, there's a second badge showing the stage where something went wrong: **Initiation**, **IPN / Notification**, or **Refund** (we explain what each one means below).
If the error came from the outside (e.g. from a payment provider), you'll see an extra badge with a short numeric code. It helps determine whether the problem was on the shop's side or the partner's side — just give this code to support.
On the right side of the row you'll see the exact moment the error happened. Handy when you want to match it to a specific order or a customer's report.
Below the badges, in a highlighted box, you'll find the full description of what happened — the most important part of the entry. If the description is long, you can scroll the box. This is where to look for a hint about what to fix.
You can select and copy the error text straight from the box. When you report a problem to support, pasting this text together with the response code and date makes help much faster.
### Payment error stages
When an entry falls under the **Payment** category, the second badge tells you which stage the problem happened at. This helps you understand the error more quickly:
Something failed right at the start — when trying to begin a payment. In practice this means the customer may not have been redirected to pay at all.
A problem receiving confirmation of payment from the provider. This notification tells the shop "the customer has paid" — when it fails, the order may not be marked as paid.
An error while trying to refund money to the customer.
## Filtering the list
When there are many errors, use the **Filtering** panel at the top to quickly find the ones you care about. You have three dropdown lists at your disposal:
Show only errors from a chosen area — e.g. just payments, just orders, or just notifications (Webhook).
Narrow payments down to a specific stage: **Initiation**, **IPN / Notification**, or **Refund**.
Show errors reported by a chosen payment provider. The list suggests the providers you have configured in your shop.
Each list has an "All…" option at the top (e.g. **All categories**, **All types**, **All gateways**) — this is the default setting, which doesn't narrow anything down. To clear a given filter, simply select that option again.
You can **combine** filters. For example, choose **Category: Payment** and **Gateway: your provider** to see only problems with one payment method. Every filter change refreshes the list below right away.
The filters you set are saved in the page address. If you refresh the panel or come back to the tab later, the list will stay narrowed down the same way — and you can even copy the link and send it to a colleague so they see exactly the same errors.
## When the list is empty
If there's nothing on the list, you'll see a **"No errors"** message noting that no problems were recorded for the selected filters. That's **good news** — either your shop is running flawlessly, or nothing simply matches the filters currently set.
If you're expecting some errors but see "No errors", check the filters first. You may have narrowed the list down, for example, to a single gateway or a single payment stage. Set everything to "All…" to see the full log.
## Common situations
Check the **Order** and **Payment** categories. For payments, pay attention to the **IPN / Notification** stage — that's the one that confirms payment. The error text usually tells you whether the problem was delivering the item or receiving the payment confirmation.
Filter by the **Webhook** category. If entries appear here, it means the messages aren't getting through — check your Discord connection settings.
Choose **Payment error type: Initiation** and the relevant **Payment gateway** to see why customers can't get to the payment step.
Look in the **AI Assistant** category — you'll find the reason why help in the panel isn't working at the moment.
## Frequently asked questions
It's the category for notifications sent to the outside — most often messages to your Discord server (e.g. an alert about a new order). If you see entries here, it means one of those notifications wasn't delivered. Check your Discord connection settings.
It's a response code from a partner (e.g. a payment provider). On its own it doesn't require any action — it's best to copy it together with the error text and pass it to support. With it, we can determine more quickly which side the problem was on.
No. The log is a history of events — entries stay, even when the problem no longer occurs. The newest errors are always at the top, so if no new entries with the same reason appear after a fix, that's a sign everything is working.
For two reasons: payments are the most common source of problems, and on top of that, older entries recorded before categories were introduced are treated as payments. Use the category filter to check.
The Errors tab is mainly about payments, so it's visible to people with access to that area of the shop. If a colleague doesn't have it in their menu, it means you haven't given them the right permissions.
An entry in the log **doesn't fix itself** — it only shows what happened. If you see repeating payment or notification errors, check the settings of the relevant gateway or your Discord connection. When the error text is unclear, copy it (together with the response code and date) and send it to support — that will speed up the help.
## Good practices
* **Check here regularly** — review the log from time to time, even when everything is working. That way you'll catch small problems early, before your customers notice them.
* **Filters first** — when you're looking for a specific problem, narrow the list down by category, payment stage, and gateway. When you see nothing, set everything to "All…".
* **Look at the date** — compare the moment of the error with a customer's report or an order number, so you can be sure it's the same case.
* **Copy the whole thing to support** — the error text, response code, and date together give support the full picture and shorten the time it takes to help.
* **React to repeats** — if the same error keeps coming back, it's not a coincidence. Check the settings of that payment gateway or your Discord connection.
* **"No errors" is a good sign** — an empty log (with filters set to "All…") means your shop is running smoothly.