> 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/monitoring-and-logs/activity-log.md).

# Activity Log

The **Activity Log** documents every business transfer between Business Central and Shopware. It is the first place to look when you want to check whether and how a synchronization ran.

**What is logged?**

* Success or failure of uploads/downloads (items, prices, inventory, customers, B2B users, categories, attributes, media, order statuses, PDF documents, and much more).
* Source and target (usually **BC → Shopware**).
* Timestamp, module, action, and a message.

**Displayed fields**

| Field           | Meaning                      |
| --------------- | ---------------------------- |
| Timestamp       | When the activity took place |
| Source / Target | Systems involved             |
| Module / Action | Type of activity             |
| BC Info         | Reference to the BC object   |
| Success         | Yes/No                       |
| Message         | Detail or error message      |

{% hint style="info" %}
For the **technical** analysis of individual API calls (URL, request, response), also use the [API Call Log](/shopware/shopware6_en_us/monitoring-and-logs/api-call-log.md).
{% endhint %}

**Cleaning up**

If required, you can clear the log from the configuration (**Delete Activity Log**).


---

# 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/shopware/shopware6_en_us/monitoring-and-logs/activity-log.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.