> 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/bestellabwicklung/wiederanlauf-duplikate-und-mehrshop-risiken.md).

# Wiederanlauf, Duplikate und Mehrshop-Risiken

Fehlerhafte Läufe dürfen nicht blind wiederholt werden.

### Wiederanlauf

1. Activity Log und API-Antwort prüfen.
2. feststellen, ob Magento/BC bereits ein Zielobjekt erzeugt hat.
3. IDs und Dashboard-Verknüpfungen prüfen.
4. Ursache beheben.
5. kleinsten Teilprozess wiederholen.

### Duplikatschutz

Die App prüft vorhandene Magento-IDs und BC-Belege. Schutz kann versagen, wenn Verknüpfungsfelder fehlen oder manuell verändert wurden.

### Mehrshop-Risiken

Einige Daten sind shopbezogen, andere globale BC-Stammdaten. Prüfen Sie Web Store Code in Dashboard, Mappings und Protokollen.

{% hint style="warning" %}
Die Katalogroutine für `website_ids` filtert in Version 27.10.0.16 nicht überall eindeutig nach Web Store Code. Testen Sie Produkt-Websites besonders sorgfältig bei mehreren Shops.
{% endhint %}

### Parallelität

Keine parallelen Läufe für denselben Shop und Bereich starten.


---

# 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/bestellabwicklung/wiederanlauf-duplikate-und-mehrshop-risiken.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.