> 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).

# WooCommerce Error Recovery

Spot and fix configurator and cart problems customers hit. Learn what the Error Recovery Center logs, what each entry shows and how to resolve issues.

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.

```mermaid
flowchart LR
    A[Customer hits a problem] --> B[Entry logged automatically]
    B --> C[Your team reviews and filters]
    C --> D[Marked as Resolved with a note]
```

***

## 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.

<table><thead><tr><th width="65.1484375">#</th><th>Where it's caught</th><th>Example</th></tr></thead><tbody><tr><td>1</td><td><strong>On the server</strong></td><td>Mimeeq can't return a price</td></tr><tr><td>2</td><td><strong>In the customer's browser</strong></td><td>The configurator fails to finish loading within 20 seconds, or hits an unexpected script error</td></tr></tbody></table>

![Error Recovery Center data grid listing logged errors with type, date and status](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

<table><thead><tr><th width="55.06640625">#</th><th>Type</th><th>What it means</th></tr></thead><tbody><tr><td>1</td><td><strong>Zero price</strong></td><td>The product loaded without a price, and your settings are configured to block adding it to the cart in that case</td></tr><tr><td>2</td><td><strong>Add to cart error</strong></td><td>Something went wrong while trying to add the configured product to the cart (often a pricing lookup that failed)</td></tr><tr><td>3</td><td><strong>Configurator not loading</strong></td><td>The 3D configurator didn't finish loading on the page</td></tr><tr><td>4</td><td><strong>Variant not available</strong></td><td>The specific variant selected isn't available</td></tr><tr><td>5</td><td><strong>JavaScript error</strong></td><td>An unexpected error occurred in the browser while the configurator was running</td></tr><tr><td>6</td><td><strong>Unknown error</strong></td><td>Doesn't fit the categories above</td></tr></tbody></table>

### What each entry contains

<table><thead><tr><th width="66.55078125">#</th><th>Detail</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><strong>Type</strong></td><td>Which of the categories above this is</td></tr><tr><td>2</td><td><strong>Error code / message</strong></td><td>A technical description, useful if you need to contact Mimeeq support</td></tr><tr><td>3</td><td><strong>Occurred at</strong></td><td>When it happened</td></tr><tr><td>4</td><td><strong>Status</strong></td><td>Unresolved or Resolved</td></tr><tr><td>5</td><td><strong>Product name</strong></td><td>The product involved, if known</td></tr><tr><td>6</td><td><strong>Page URL</strong></td><td>The page the customer was on</td></tr><tr><td>7</td><td><strong>Short code / Template ID</strong></td><td>Which configurator was involved</td></tr></tbody></table>

{% hint style="info" %}
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.
{% endhint %}

***

## 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

* **Prioritise:** errors that seem to be affecting many customers, not only 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 only in WordPress)

{% hint style="info" %}
Email notifications for these same problems are configured separately — see [WooCommerce Error Notifications](/commerce-and-integrations/woocommerce/error-notifications.md).
{% endhint %}

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>WooCommerce Error Notifications</strong></td><td>Email your team when configurator or cart errors happen.</td><td><a href="/commerce-and-integrations/woocommerce/error-notifications.md">WooCommerce Error Notifications</a></td></tr><tr><td><strong>WooCommerce Storefront Setup</strong></td><td>Add the configurator with Gutenberg blocks, Elementor or shortcodes.</td><td><a href="/commerce-and-integrations/woocommerce/storefront-setup.md">WooCommerce Storefront Setup</a></td></tr><tr><td><strong>WooCommerce Getting Started</strong></td><td>Install the plugin, add your API key and sync products.</td><td><a href="/commerce-and-integrations/woocommerce/getting-started.md">WooCommerce Getting Started</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
