Output panel

Inspect Sync, Watcher, and Debug output from the Main page.

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

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

Output tabs on the Main page for sync runs, watcher activity, and debug logs.

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 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 after a sync finishes.

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

The log buffer lives only in memory.

Restarting CrossWatch clears it.

Collect the Debug output before you restart the container.

Collect logs for support

When you report a sync or provider problem:

1

Reproduce the problem

Run the sync or playback flow that shows the issue.

2

Open the Output panel

Go to Main.

Open View details.

Select Debug.

3

Wait for the run to finish

Let the affected sync complete or fail.

4

Copy the output

Click Copy.

Paste the full output into the support request.

Prefer a code block or a text file.

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.

CrossWatch redacts known credential fields.

Review the output before sharing it.

Logs can still contain media titles, account names, server addresses, and provider identifiers.

Related topics

• Main dashboard
• Status dashboard
• Navigation
• Maintenance
• Events
• Synchronization
• Watcher