> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/output-panel.md).

# Output panel

The **Output panel** on **Main** shows live text output from CrossWatch.

Use it to inspect sync runs, Watcher activity, and diagnostic messages.

<figure><img src="/files/ynmop8cFqV19btoYgjUc" alt=""><figcaption><p>Output tabs on the Main page for sync runs, watcher activity, and debug logs.</p></figcaption></figure>

### Tabs

The Output panel includes three tabs:

* **Sync** — output from sync runs
* **Watcher** — output from Watcher and scrobble activity
* **Debug** — combined diagnostic output for troubleshooting

### Understand sync results

Use [Sync statuses](/crosswatch/main-dashboard/output-panel/sync-statuses.md) to read counters and outcomes such as:

* `added`, `removed`, and `updated`
* `skipped`, `blocked`, and `unresolved`
* `attempted`, `pairs`, and compact summaries like `+8 / -2 / ~4`

### Debug output

The **Debug** tab shows diagnostic messages from CrossWatch and its provider modules.

It also includes sync and watcher-related output in one place.

Provider logs still appear in the Docker console.

CrossWatch also copies provider log output into the **Debug** tab.

### What the Debug tab shows

Each entry includes a timestamp and a source tag.

The output can show:

* which provider operation ran
* which sync stage was reached
* provider responses and status codes
* skipped or unsupported operations
* rate limits and authentication problems
* matching and metadata problems
* exceptions and processing failures

### How the Debug tab works

CrossWatch keeps recent diagnostic messages in an in-memory buffer.

When you open **Debug**, CrossWatch loads the buffered messages first.

New messages then stream into the tab in real time.

The Debug tab:

* follows new messages automatically
* reconnects if the stream drops
* lets you copy the current tab with **Copy**

Use [Events](/crosswatch/main-dashboard/tools/events.md) after a sync finishes.

Events keeps searchable run history, related attempts, and recorded reasons.

{% hint style="warning" %}
The log buffer lives only in memory.

Restarting CrossWatch clears it.

Collect the **Debug** output before you restart the container.
{% endhint %}

### Collect logs for support

When you report a sync or provider problem:

{% stepper %}
{% step %}

### Reproduce the problem

Run the sync or playback flow that shows the issue.
{% endstep %}

{% step %}

### Open the Output panel

Go to **Main**.

Open **View details**.

Select **Debug**.
{% endstep %}

{% step %}

### Wait for the run to finish

Let the affected sync complete or fail.
{% endstep %}

{% step %}

### Copy the output

Click **Copy**.

Paste the full output into the support request.

Prefer a code block or a text file.
{% endstep %}
{% endstepper %}

The **Copy** button copies the currently selected tab.

If you are on **Debug**, it copies **Debug** output.

### What to include with the logs

Also include:

* your CrossWatch version
* the providers involved
* what you expected to happen
* what actually happened

### When Debug output is required

Use **Debug** output for support requests involving:

* sync failures
* missing items
* provider errors
* unexpected sync results

Without the relevant Debug output, it is often not possible to identify the failing provider request, matching decision, or sync stage.

{% hint style="warning" %}
CrossWatch redacts known credential fields.

Review the output before sharing it.

Logs can still contain media titles, account names, server addresses, and provider identifiers.
{% endhint %}

### Related topics

* [Main dashboard](/crosswatch/main-dashboard.md)
* [Status dashboard](/crosswatch/main-dashboard/status-dashboard.md)
* [Navigation](/crosswatch/main-dashboard/navigation.md)
* [Maintenance](/crosswatch/settings/maintenance.md)
* [Events](/crosswatch/main-dashboard/tools/events.md)
* [Synchronization](/crosswatch/settings/synchronization.md)
* [Watcher](/crosswatch/settings/scrobbler/watcher.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://wiki.crosswatch.app/crosswatch/main-dashboard/output-panel.md?ask=<question>&goal=<endgoal>
```

`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.