> 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/fehlerbehebung-and-support/haufige-fehlerbilder.md).

# Häufige Fehlerbilder

### Verbindungstest schlägt fehl

URL/API-Pfad, Benutzer, Passwort, Magento-Rechte, TLS, WAF und Antwortstatus prüfen. OAuth in Version 27.10.0.16 nicht ohne Korrektur nutzen.

### Download Cockpit zeigt Blocker

Refresh Preconditions ausführen und Blocking Reason bearbeiten. Häufig fehlen Verbindung, Initialdaten oder Mappings.

### Auftrag wird nicht geladen

Allows Order Download, Downloadable Order Status, Start From Order ID und API-Filter prüfen. Der Selected-Haken ist nicht maßgeblich.

### Auftrag ohne richtigen Kunden

Kundenmapping, Standardkunden, Create Unknown Customer und Vorlage prüfen; Name/Adresse manuell kontrollieren.

### Produkt ohne Preis/Variante

Artikeltyp, Attribute Set, Achsen, Optionswerte und dokumentierte Variantenlimits prüfen.

### Bestand falsch

MSI-Quelle/Lagerort, SKU, Artikelposten, negative Menge und letzten Batch kontrollieren.

### Gutschrift erzeugt falschen Beleg

{% hint style="danger" %}
Bekannter Fehler: Blanket Order statt Verkaufsgutschrift. Aktion stoppen und freigegebenen manuellen Prozess verwenden.
{% 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/fehlerbehebung-and-support/haufige-fehlerbilder.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.