> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/troubleshooting-and-support/common-error-patterns.md).

# Common Error Patterns

### Connection Test Fails

Check URL/API path, user, password, Magento permissions, TLS, WAF, and response status. Do not use OAuth in version 27.10.0.16 without a fix.

### Download Cockpit Shows a Blocker

Run Refresh Preconditions and address the Blocking Reason. Common causes are missing connection, initial data, or mappings.

### Order Is Not Downloaded

Check Allows Order Download, Downloadable Order Status, Start From Order ID, and API filters. The Selected check mark is not authoritative.

### Order Without the Correct Customer

Check customer mapping, default customers, Create Unknown Customer, and the template; manually verify name/address.

### Product Without Price/Variant

Check item type, Attribute Set, axes, option values, and the documented variant limits.

### Incorrect Inventory

Check MSI source/location, SKU, Item Ledger Entries, negative quantity, and the last batch.

### Credit Memo Creates the Wrong Document

{% hint style="danger" %}
Known bug: creates a Blanket Order instead of a Sales Credit Memo. Stop the action and use the approved manual process.
{% endhint %}


---

# 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://docs.solutioo.de/magento-2-api-connector/magento2_en_us/troubleshooting-and-support/common-error-patterns.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.
