> 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

Find missing, mismatched, unresolved, blocked or unhealthy sync items.

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

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

On mobile, use **Filters and sorting** beside search to expand the feature, provider and sorting controls.

### Select a sync pair

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

Analyzer opens on the pair you selected last time. If there is none, it opens on the pair that ran most recently.

**Saved snapshots** shows the last sync time for the selected scope.

Select **Analyze** to refresh the item results and the system health checks.

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

### Notices

Notices appear above the results when something needs attention:

* **Some pair comparisons are unavailable**: a provider has no saved snapshot for that pair and feature. Run the pair to read both sides.
* **System failures or warnings need attention**: select **View findings** to open System health.
* **Item analysis could not finish** or **System health could not be checked**: select **Retry**.

### Views

Each view shows a count once the analysis finishes. On smaller screens, use **View** to switch views. Select a result to open its details, then use **Back to results** to return to the list.

#### Snapshot differences

Shows items found on one side of a sync pair but not confirmed on the other side, and History entries whose watch times do not match.

The **Finding** column tells you what was found:

| Finding                         | Meaning                                                                                         |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Missing at …**                | The item is in the source snapshot but not confirmed at that destination.                       |
| **Watch time differs at …**     | The item exists on both sides, but no recorded watch time matches.                              |
| **Grouped watches missing**     | An episode group is complete at the source, but the destination is missing the grouped watches. |
| **Waiting for remaining parts** | Not all separate parts of an episode group have been watched yet.                               |
| **Episode group held**          | An episode group cannot be synced. The details show the reason.                                 |

History deliberately excluded by a pair’s dropped-show settings or active Trakt rewatch reset is left out of its missing-item comparisons. Run the pair after changing those settings so Analyzer has its current exclusions.

A missing snapshot is not treated as an empty provider. If CrossWatch does not have enough saved data, the view shows **Comparison incomplete**.

{% hint style="info" %}
A watch time difference does not prove a missing watch. Matching IDs do not establish whether it is the same playback or a separate watch.
{% endhint %}

#### 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
* the write was not confirmed by the provider
* a provider limit was reached

Each item shows one of two states:

* **Pending retry**: CrossWatch tries again on the next sync.
* **Automatic retries blocked**: the item failed repeatedly, so CrossWatch stopped retrying it.

Select an item to see the reason and available IDs.

#### System health

Shows CrossWatch health findings related to providers, the orchestrator and saved sync state, plus findings for the selected pairs.

Findings can be:

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

Findings that cover several items have an **Affected items** list you can expand.

Typical pair findings include:

* **Same episode number, different episode**: both sides use the same season and episode number for different episodes.
* episode groups that are waiting or held
* items with invalid or missing cross-provider IDs
* anime mapping that is disabled or not ready

Global system diagnostics are available to administrators only. Pair findings stay visible for other users.

#### Blocked items

Shows items CrossWatch is intentionally preventing from syncing.

This can include:

* manual blocks created in Editor
* blocks created by a saved mapping correction
* 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. Rating and progress values may differ even when an item exists on both sides.

### Fix items

With write permission, Analyzer shows action buttons on the results. All actions change saved CrossWatch rules only. Run the pair again afterwards, then select **Analyze**.

Actions apply to one sync pair. If **All sync pairs** is selected and an item has no pair, select the pair first.

#### Edit mapping

In **Snapshot differences** and **Pending retries**, select the pencil icon to correct a mapping.

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

The pencil is not shown for:

* watch time differences, because a mapping edit does not correct a watch time
* episodes that belong to an episode group. Manage these in **Editor → Mappings & blocks → Episode groups**
* items missing at more than one destination

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

#### Fix matching

For movies, select the search icon to let CrossWatch look the film up at the destination.

CrossWatch checks the items already synced, then the destination catalogue by ID and by title. It shows what it checked and what it found.

* Select **Use this match** to save the proposed match.
* Select **Search manually** to open the mapping dialog instead.

For **Same episode number, different episode** findings in System health, select **Fix matching** to open the episode numbering review for that show.

#### Release retry block

For items marked **Automatic retries blocked**, select the open lock icon to release the block.

The item is retried on the next sync. It is blocked again if the same failure repeats, so resolve the cause first.

If you save a mapping for such an item, Analyzer offers **Release retry block** right after saving.

#### Release block or remove mapping

In **Blocked items**, manual blocks have a button:

* **Release block**: removes the manual block so the item can sync again.
* **Remove mapping**: shown when the block belongs to a saved mapping correction. This undoes the correction and lifts the block on the original item.

{% hint style="warning" %}
If Analyzer reports that the item changed, select **Analyze** and try again.
{% endhint %}

### Item details

Select an item to view available details such as:

* title
* provider and sync pair
* feature
* year
* current status
* what happened
* suggested next step
* item IDs

For watch time differences, the details show the source watch time, the closest recorded watch at the destination, and the difference between them.

For episode groups, the details show how many parts are watched on each side and any hold reason.

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
* anime-only sync

When exclusions apply, Analyzer shows a scope note with the number of excluded items per pair and feature.

### Filters

Use the toolbar to filter results by:

* search, across titles, IDs, providers and reasons
* feature
* severity, in System health
* sort order: title, provider or feature

Select **Clear filters** to reset them. Filters also reset when you switch views.

Use **Per page** to show 25, 50, 100 or 250 results.

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 or fix the matching when needed.
6. Release the retry block if automatic retries are blocked.
7. Check **Blocked items**.
8. Check **System health**.
9. Run the pair again.
10. Analyze again.

Use **Snapshot differences** when you want to compare presence and watch times between the saved source and destination state.

### Important

Analyzer does not:

* run a sync
* apply changes to providers
* remove provider items
* retry an item when you save a mapping or release a block
* 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.

### Sync failure details

Open an item’s detail panel to read **What happened**. When the provider recorded ambiguous matches, **Possible matches from previous attempt** shows candidate titles and IDs, up to 10 entries. Compare these with the source before correcting metadata or retrying. The details describe the recorded attempt; they are not a fresh provider check.

### Unknown watch dates

A history difference can be an expected skip when the destination cannot preserve an unknown watch date, or when Rewatches is enabled for an undated watch. Read the reason before retrying or changing mappings. A watched item with no original date is not necessarily a bad match. See [Unknown watch dates](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md#unknown-watch-dates).


---

# 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://wiki.crosswatch.app/crosswatch/main-dashboard/tools/analyzer.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.
