> 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/shopware/shopware6_en_us/frequently-asked-questions-faq/faq-synchronization-and-errors.md). # FAQ – Synchronization & Errors ### How do I automate uploads and downloads? Via the **Job Queue** in Business Central. It allows you to schedule the order retrieval, the item, price, and inventory upload, as well as the status feedback. You will find concrete examples under [Recommended Job Queue Setups](/shopware/shopware6_en_us/automation-and-schedules/recommended-job-queue-setups.md). ### Where can I see whether a synchronization was successful? In the **Activity Log** you can see every functional transfer with its success/error status. For technical details (URL, request, response), enable the **API Call Log**. See [Activity Log](/shopware/shopware6_en_us/monitoring-and-logs/activity-log.md) and [API Call Log](/shopware/shopware6_en_us/monitoring-and-logs/api-call-log.md). ### An upload fails repeatedly – how do I find the cause? Open the relevant entry in the **API Call Log** and read the Shopware response (the `errors` or `detail` field). It states the specific cause, for example a missing mandatory field. See [Analyze API Responses](/shopware/shopware6_en_us/monitoring-and-logs/analyze-api-responses.md). ### Why is a record synchronized again? Every change to an item, price, customer, or address automatically sets the record to **not synchronized**. It is therefore transferred again during the next run – this keeps the shop up to date. ### What do the Shopware error codes 400, 404, and 409 mean? **400** stands for a validation issue (missing mandatory field/invalid value), **404** for an object that was not found (check the Web ID/mapping), and **409** for a duplicate (check the matching/Web ID). You will find an overview under [Analyze API Responses](/shopware/shopware6_en_us/monitoring-and-logs/analyze-api-responses.md). ### How do I enable technical API logging? Via the **Enable Developer Log** configuration setting. In the case of HTTP errors, an entry is forced even when logging is switched off. Enable it deliberately for troubleshooting, because a large number of entries accumulate during continuous operation. ### How do I make a clean restart after serious errors? Use the graduated **reset functions** – from individual mappings through to a complete reset. Back up the configuration by exporting it beforehand. See [Clean Restart via Reset](/shopware/shopware6_en_us/onboarding-and-best-practices/clean-restart-via-reset.md). ### Does the synchronization run automatically in Business Central Cloud? Yes. Automation is handled by Job Queue Entries, which run both in the cloud and on-premises. Stagger the start times so that several large runs do not start at the same time. ### How do I automate the synchronization? Using the Job Queue in Business Central, you set up scheduled tasks for item, price, inventory, and order synchronization. You will find recommended intervals and sequences under [Recommended Job Queue Setups](/shopware/shopware6_en_us/automation-and-schedules/recommended-job-queue-setups.md) and [Scheduler & AutoSync](/shopware/shopware6_en_us/automation-and-schedules/scheduler-and-autosync.md). ### Where can I see why an upload failed? You can see failed uploads and the exact Shopware response in the **API Call Log** as well as in the [Bulk Upload Report (Shopware Upload Data)](/shopware/shopware6_en_us/automation-and-schedules/bulk-upload-report-shopware-upload-data.md). There you will find the status code, endpoint, and error message for a targeted analysis. For details, see [API Call Log](/shopware/shopware6_en_us/monitoring-and-logs/api-call-log.md) and [Analyze API Responses](/shopware/shopware6_en_us/monitoring-and-logs/analyze-api-responses.md). ### What does an HTTP error 400 during synchronization mean? A **400 Bad Request** indicates invalid or missing data, for example a mandatory field without a value, an unmapped tax, or an invalid sales channel. Check the affected field values and mappings and repeat the upload. The server response in the API Call Log usually names the specific field. ### How do I repeat failed operations? After you have resolved the cause, you can upload the affected record again or restart the job in the Job Queue. The bulk upload report helps you reprocess all affected records together. For details, see [Error Handling in Automatic Processes](/shopware/shopware6_en_us/automation-and-schedules/error-handling-in-automatic-processes.md). ### Can the automation process orders and items at the same time? Yes, you can schedule several tasks in parallel or staggered in time. Pay attention to sensible intervals and sequences (for example, master data first, then prices/inventory, then orders) in order to take the API load and dependencies into account. For details, see [Recommended Job Queue Setups](/shopware/shopware6_en_us/automation-and-schedules/recommended-job-queue-setups.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.solutioo.de/shopware/shopware6_en_us/frequently-asked-questions-faq/faq-synchronization-and-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.