> 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/status-and-log-meanings.md).

# Status and Log Meanings

### Synchronization Status

* **Synced = Yes**: last documented run was successful
* **Synced At**: timestamp of that run
* **Magento ID**: stored target/source ID
* **Status Reason**: last message or error cause

### Cockpit Status

* **Ready**: preconditions met according to rules
* **Blocking Reason**: currently detected blocker
* **Running**: processing active
* **Completed / Last Status = OK**: dispatcher run finished
* **Failed**: preflight or execution error
* **Last Count**: reported record count

{% hint style="warning" %}
A green cockpit row is not reliable proof of success. In version 27.10.0.16, Last Status can show OK even with zero results, partial API errors, or areas without a handler.
{% endhint %}

### HTTP Status

2xx accepted, 400/422 validation, 401 authentication, 403 authorization, 404 path/ID, 409 conflict, 429 rate limit, 5xx server/proxy.

### Interpretation

Status fields are not a real-time comparison. For critical operations, verify the record, Product Download Log, Activity/API Log, and the Magento target state.


---

# 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/status-and-log-meanings.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.
