> 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/use-the-download-cockpit.md).

# Use the Download Cockpit

The **Magento Download Cockpit** consolidates reference, catalog, and sales downloads. Each row shows preconditions, run order, and the result of the last run.

### Three Presets — One Start Button

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>🧭 Run Initial Setup</strong></td><td>Marks reference data for initial setup.</td></tr><tr><td><strong>🛍️ Run Catalog Sync</strong></td><td>Marks categories, details, and category products.</td></tr><tr><td><strong>🧾 Run Sales Sync</strong></td><td>Marks orders and optionally credit memos.</td></tr></tbody></table>

{% hint style="info" %}
Presets only set selection checkmarks. Only **Run Selected** executes the marked areas in their Run Order.
{% endhint %}

### Execute Safely

{% stepper %}
{% step %}
**Check webshop and selection**

Enable only the required areas; for diagnostics, select a single area whenever possible.
{% endstep %}

{% step %}
**Run Refresh Preconditions**

Read Ready and Blocking Reason. Resolve red blockers before starting.
{% endstep %}

{% step %}
**Verify Run Order**

Process reference data before catalog, catalog before sales processes.
{% endstep %}

{% step %}
**Start Run Selected**

Do not start the run a second time in parallel.
{% endstep %}

{% step %}
**Verify results at business level**

Compare Last Count, Message, Product Download Log, Activity/API Log, and the target state.
{% endstep %}
{% endstepper %}

### Evaluate Status Correctly

| Display        | States                      | Not proof of                        |
| -------------- | --------------------------- | ----------------------------------- |
| Ready          | local preconditions met     | complete Magento permissions        |
| Completed / OK | dispatcher finished the run | processed records or error-free API |
| Last Count = 0 | no reported results         | an error or actual data shortage    |
| Failed         | preflight or runtime error  | automatically clean restart         |

{% hint style="warning" %}
The separate **Product Images** and **Related Items** areas have no execution handler in version 27.10.0.16. Images can be processed within the product download; related items via the designated upload actions.
{% endhint %}

<details>

<summary><strong>Last Count is 0 — what now?</strong></summary>

Check filters, Magento source data, Message, and the API Log. For products, additionally open the Product Download Log. A green row with Count 0 is not sufficient proof of success.

</details>


---

# 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/use-the-download-cockpit.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.
