> 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/download-and-automation-overview.md).

# Download & Automation Overview

The **Magento Download Cockpit** consolidates all available download areas. Each row shows preconditions, last status, result count, run time, and message.

### Areas

Initial data, payment/shipping methods, websites, store views, taxes, attributes, customer groups, statuses, categories, products, MSI sources, orders, credit memos, and option structure are controlled separately.

### Presets

* **Run Initial Setup** marks the setup areas.
* **Run Catalog Sync** marks categories, details, and category products.
* **Run Sales Sync** marks orders and credit memos.
* **Run Selected** actually executes the enabled rows in Run Order.

{% hint style="info" %}
The three presets do not start a download. Always run **Run Selected** afterwards.
{% endhint %}

### Automation

The product download is resumable. **Max Products Per Run** controls the batch size; the default is 50. The cockpit can create a recurring product download job.

### Status Display Limitations

* The **Product Images** and **Related Items** areas have preflight and cockpit rows in version 27.10.0.16 but no execution handler.
* **Last Status = OK** does not reliably confirm that data was processed or that every API call succeeded.
* For products, the **Product Download Log** is authoritative; for other areas, additionally check the Activity Log, API Log, and the target system.

{% hint style="warning" %}
Not every codeunit with Job Queue Entry metadata has an executable background process. Only use explicitly verified automations.
{% 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/download-and-automation-overview.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.
