⌘Ctrlk
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.
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 and API Call Log.
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.
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.
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.
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.
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.
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.
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 and Scheduler & AutoSync.
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). There you will find the status code, endpoint, and error message for a targeted analysis. For details, see API Call Log and Analyze API Responses.
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.
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.
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.