> 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/tools/analyzer.md).

# Analyzer

Analyzer helps you find missing, unresolved, blocked or unhealthy sync items.

It uses saved CrossWatch sync data. It does not run a sync or change provider data.

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FuJb1DoT8xQ3YQHVXiVvO%2Fimage.png?alt=media&amp;token=8ee214fc-164d-4d3a-bb53-b338049436dc" alt=""><figcaption></figcaption></figure>

### Select a sync pair

Choose a sync pair at the top of the page, or select **All sync pairs**.

Select **Analyze** to refresh the results.

{% hint style="info" %}
Analyzer uses saved sync snapshots. If the data looks outdated, run the affected sync pair first and analyze again.
{% endhint %}

### Views

#### Missing items

Shows items found on one side of a sync pair but not confirmed on the other side.

A missing snapshot is not treated as an empty provider. If CrossWatch does not have enough saved data, the comparison is shown as incomplete.

#### Pending retries

Shows items that could not be matched or written during a previous sync.

Common reasons include:

* no matching item was found
* provider IDs do not match
* season or episode numbering differs
* the provider rejected the update
* a provider limit was reached

Select an item to see the reason and available IDs.

**Correct a mapping**

For supported pending retries, select the pencil icon to correct the mapping.

You can correct titles, IDs, seasons or episodes using the same mapping dialog as Interactive Sync.

After saving the mapping:

1. Run the affected sync pair again.
2. Return to Analyzer.
3. Select **Analyze** again.

{% hint style="info" %}
Saving a mapping does not retry the item immediately.
{% endhint %}

#### System health

Shows CrossWatch health findings related to providers, sync state and diagnostics.

Findings can be:

* **Error**
* **Warning**
* **Information**

Global system diagnostics are available to administrators only.

#### Blocked items

Shows items CrossWatch is intentionally preventing from syncing.

This can include:

* manual blocks created in Editor
* automatic protection rules

Blocked items are not deleted from the provider.

#### All items

Shows all saved items in the selected pair scope.

Use this view to inspect items that are not currently missing, pending or blocked.

### Item details

Select an item to view available details such as:

* title
* provider
* feature
* year
* item IDs
* current status
* reason
* suggested next step

For Watchlist and Collection items, Analyzer can also show known provider limits.

### Pair rules

Analyzer follows the configured sync rules for the selected pair.

Items can be excluded by:

* media type
* library
* feature
* direction

When exclusions apply, Analyzer shows a scope note.

### Filters

Use the toolbar to filter results by:

* search
* feature
* severity, in System health
* sort order

Analyzer supports History, Watchlist, Ratings, Progress and Collection.

### Recommended workflow

When an item does not sync:

1. Select the affected pair.
2. Select **Analyze**.
3. Check **Pending retries**.
4. Review the reason and IDs.
5. Correct the mapping when needed.
6. Check **Blocked items**.
7. Check **System health**.
8. Run the pair again.
9. Analyze again.

Use **Missing items** when you want to compare presence between the saved source and destination state.

### Important

Analyzer does not:

* run a sync
* apply changes to providers
* remove provider items
* treat a missing snapshot as an empty provider
* guarantee that saved data matches the provider's current live state

Use Interactive Sync when you want to review the actual changes planned for a sync.


---

# 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/tools/analyzer.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.