> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/commerce-and-integrations/woocommerce/error-recovery.md).

# Error Recovery

How the Mimeeq Error Recovery Center logs configurator and cart issues automatically — error types, filtering, and marking issues resolved.

## Overview

The Error Recovery Center is an automatic log of technical problems that happen while customers use the 3D configurator or try to add a product to their cart. Think of it as a diagnostic notebook your team can check when something isn't working as expected — every entry is recorded automatically, with no action needed from you or the customer.

***

## Accessing the Tool

1. Log in to **WP Admin**
2. Open the **Mimeeq** menu
3. Select **Error Recovery Center**

***

## What Gets Logged, and When

Every entry is created automatically by the plugin — nothing here relies on a customer filling in a form. Some problems are caught immediately on the server (for example, when Mimeeq can't return a price); others are reported by the configurator running in the customer's browser (for example, when it fails to finish loading within 20 seconds, or hits an unexpected script error).

![Screenshot: Error Recovery Center data grid](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FZeDSvgVuA9YENV0fhYyu%2F04-error-recovery-center-01-da_1ryqsz.png?alt=media)

## Error Types

| Type                     | What it means                                                                                                    |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| Zero price               | The product loaded without a price, and your settings are configured to block adding it to the cart in that case |
| Add to cart error        | Something went wrong while trying to add the configured product to the cart (often a pricing lookup that failed) |
| Configurator not loading | The 3D configurator didn't finish loading on the page                                                            |
| Variant not available    | The specific variant selected isn't available                                                                    |
| JavaScript error         | An unexpected error occurred in the browser while the configurator was running                                   |
| Unknown error            | Doesn't fit the categories above                                                                                 |

## What Each Entry Contains

| Detail                       | Description                                                           |
| ---------------------------- | --------------------------------------------------------------------- |
| **Type**                     | Which of the categories above this is                                 |
| **Error code / message**     | A technical description, useful if you need to contact Mimeeq support |
| **Occurred at**              | When it happened                                                      |
| **Status**                   | Unresolved or Resolved                                                |
| **Product name**             | The product involved, if known                                        |
| **Page URL**                 | The page the customer was on                                          |
| **Short code / Template ID** | Which configurator was involved                                       |

There are also fields reserved for a customer's contact details (name, email, comment) — at the moment there's no on-site form for customers to fill these in themselves, so in practice you'll usually see these left blank.

***

## Managing Errors

### Filtering

Narrow down the list by:

* **Status** (All / Unresolved / Resolved)
* **Error type** — useful for spotting patterns, like the same product repeatedly failing to load

### Marking Errors as Resolved

Open an entry to change its status to **Resolved** and leave yourself an internal note describing what you did about it.

***

## Best Practices

* **Prioritize** errors that seem to be affecting many customers, not just one
* **Write yourself a note** each time you resolve something, so the next person (or future you) knows what was tried
* **Look for repeat offenders** — the same product or page showing up again and again usually points to something worth fixing at the source (in your Mimeeq configuration, not just in WordPress)

***

## Notes

* Email notifications for these same problems are configured separately — see [Error Notification Emails](/commerce-and-integrations/woocommerce/error-notifications.md)

***

## Related Articles

* [Error Notification Emails](/commerce-and-integrations/woocommerce/error-notifications.md)
* [Gutenberg Blocks & Elementor Widgets](/commerce-and-integrations/woocommerce/storefront-setup.md)
* [Getting Started](/commerce-and-integrations/woocommerce/getting-started.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.mimeeq.com/commerce-and-integrations/woocommerce/error-recovery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
