Analyzer
Inspect sync gaps, blocked items, scope exclusions, weak identifiers, provider limits, and local state diagnostics.
Inspect sync gaps, blocked items, scope exclusions, weak identifiers, provider limits, and local state diagnostics.
The Sync Analyzer compares the current CrossWatch state for one or more selected sync pairs.
Use it to determine:
Which items are missing from a destination
Which route is affected
Why an item may not have synchronized
Whether an item is manually blocked
Whether pair settings excluded an item
Whether provider limits prevented an addition
Whether local state or metadata contains inconsistencies
The Analyzer helps identify the cause of a sync problem.
It does not automatically correct metadata stored in Plex, Jellyfin, Emby, Trakt, or another provider.
Requirements
Before using the Analyzer:
Run the affected sync pair at least once
Confirm that the pair is enabled
Confirm that the required feature is enabled
Analyzer reads the current local provider and sync state generated by CrossWatch.
When no scoped state is available, run a sync for the selected pair and reopen Analyzer.
Optional metadata integrations can improve the quality of IDs and matching elsewhere in CrossWatch, but they are not required to open Analyzer.
Open Analyzer
Open the Sync Analyzer from the CrossWatch interface.
The Analyzer loads:
Configured sync pairs
Current provider state
Pair routes and enabled features
Missing peer results
Manual block state
Pair scope exclusions
Normalization findings
Provider and state diagnostics
The initial analysis can take longer when the local state contains many items.
Analyzer layout
The current Analyzer contains:
View selector
Sync pair selector
Analysis status
Provider item counts
Result summary
Search
Show IDs control
Result table
Resizable detail panel
Analyze button
Views
Needs attention
Needs attention is the default view.
It contains items that are missing, unresolved, risky, or otherwise require review for at least one selected route.
Typical results include:
An item exists at the source but is missing at a destination
One destination is missing an item while another destination is aligned
A provider limit prevented an item from being added
IDs are incomplete or inconsistent
A route has a matching or normalization problem
The Analyzer compares selected routes independently.
An item being present at one destination does not hide a gap at another destination.
All scoped items
All scoped items displays the current provider state for the selected routes.
It includes both healthy and affected items.
Use this view to:
Confirm that an item is present in local state
Inspect IDs for an item without an active issue
Compare healthy and missing items
Review the full scope used by the selected pairs
Results are loaded in pages of up to 250 items.
Use Previous and Next to move between pages.
Sync pair selection
The Sync pairs section controls which routes are analyzed.
You can select one or more pairs.
Analyzer only includes enabled pairs and enabled features.
Supported analyzed features include:
History
Watchlist
Ratings
Progress
For a one-way pair, Analyzer checks the configured source-to-destination route.
For a two-way pair, Analyzer checks both directions.
Provider profiles are shown with their instance name when a non-default profile is used.
For example:
PLEX@Family → TRAKT@Primary
Analysis status
The sidebar displays three status counters.
Issues
Issues is the number of missing peer results found for the selected routes.
The counter can also show totals by feature:
H, HistoryW, WatchlistR, RatingsP, Progress
System
System is the number of background diagnostics reported by the Analyzer.
System findings can describe state, cache, metadata, provider, or integrity conditions.
A System finding does not always mean that an item is currently unsynchronized.
It can still explain why a route is unstable or why matching is unreliable.
Blocked
Blocked is the number of scoped items currently covered by manual block rules.
Blocked items are identified separately from normal missing peer issues.
Summary counters
The result header displays the current analysis totals.
Scoped
Scoped is the total number of items in the current Analyzer view for the selected pairs.
In Needs attention, this is the number of issue items.
In All scoped items, this is the total number of provider state items in scope.
Visible
Visible is the number of rows currently displayed after applying:
The selected view
The selected page
Pair scope
Search text
Issues
Issues is the total number of missing peer results for the selected routes.
System
System is the number of background diagnostic findings.
Analysis time
When available, Analyzer also displays the server analysis time in milliseconds.
Result table
The result table contains:
Provider
Feature
Title
Type
Select a column heading to sort the table.
Selecting the same heading again reverses the sort direction.
The table supports sorting by:
Provider
Feature
Title
Type
Episode titles are displayed with their series and episode number.
Example:
Series Name, S02E05
Season entries are displayed with their series and season number.
Example:
Series Name, S02
Search
Use Search to filter the rows on the current page.
Search checks:
Provider
Feature
Title
Display title
Year
Media type
Multiple search words must all be present in the row data.
Search does not query connected providers.
It only filters the data already loaded into Analyzer.
Show IDs
Select Show IDs to display known item identifiers below each title.
Supported fields can include:
IMDb
TMDb
TVDb
MAL
AniList
Trakt
Plex
Simkl
Emby
MDBList
PublicMetaDB
Missing or incorrect IDs can cause matching failures, especially when providers use different primary identifiers.
Result indicators
Missing indicator
An issue row displays an indicator when the item is missing at another provider.
Hover over the indicator to see:
The missing destination
The first available reason
When several destinations are selected, the result can identify more than one missing target.
Blocked indicator
A blocked label means the item is covered by a manual block rule.
Manual blocks are loaded from the Editor state for the same provider and feature.
Blocked items are counted separately and are not treated as normal missing peer issues.
Detail panel
Select a result row to open its details.
The detail panel can contain:
Item title and year
Missing destination
Analyzer reason
Blocked status
Known IDs
Provider limit information
History normalization findings
Pair scope exclusions
System findings for the selected item
Other system findings
The divider between the result table and detail panel can be dragged to resize both areas.
The selected size is stored in the browser.
Issue reasons
Analyzer can provide a reason from the destination or matching analysis.
Possible reasons include:
Missing at the destination
Item could not be resolved
Weak or missing IDs
Target lookup failed
Item was excluded by pair scope
Provider account limit reached
Manual blocking
Suggestions and reason messages are diagnostic hints.
Verify the item in the source and destination before changing metadata or removing data.
Provider limits
Analyzer can detect supported provider account limits from current provider status.
For example, when a Trakt account reaches a Watchlist or Collection limit, the detail panel can show:
The affected provider
The affected feature
Current usage
Account limit
Number of affected Analyzer items
The last known limit error
When a provider limit has been reached, correcting IDs will not allow additional items to be added until capacity is available.
Remove items from the destination or change the provider account plan before rerunning the pair.
Scope exclusions
Analyzer can report items excluded by pair configuration.
Scope exclusions can be caused by:
Disabled media types
Feature type restrictions
Pair direction
Disabled features
Other pair-specific scope settings
The detail panel can show:
Source
Destination
Feature
Number of excluded items per media type
Allowed media types
An excluded item is not necessarily a sync failure.
It can be working as configured.
System findings
System findings are background diagnostics produced during analysis.
They can include conditions involving:
State files
Provider cache
Unresolved item records
Blackbox state
Tombstones
Flapping protection
Watermarks
Provider modules
Missing identifiers
Duplicate or conflicting identifiers
History show normalization
Metadata consistency
Provider validation
Some findings include affected item lists and internal state values.
System findings are divided into:
Findings related to the selected item
Other findings from the current analysis
The related findings section opens automatically for the selected result.
Other findings remain collapsed until opened.
History normalization
Analyzer can report History show normalization findings.
These findings describe cases where show, season, and episode state required normalization or contains inconsistent structure.
Use these findings when:
Episode History does not align
A show appears under inconsistent keys
Provider History contains mixed show and episode data
Matching succeeds for a show but fails for its episodes
Normalization findings do not always indicate an active missing item.
They provide context for History matching and state structure.
Edit Manual IDs
The detail panel allows known identifiers to be edited for the selected local Analyzer item.
Use this when the current state contains weak, missing, or incorrect IDs.
The editor supports the Analyzer ID fields shown for the item.
Save behaviour
Saving Manual IDs:
Sends the provider, feature, item key, and ID values to the Analyzer patch endpoint
Removes empty ID values
Allows the item key to be rebuilt from the new IDs
Does not automatically merge identifiers from peer items
Runs Analyzer again after saving
Selects the updated item when its key changes
The change updates CrossWatch local runtime state.
It does not directly edit metadata in Plex, Jellyfin, Emby, Trakt, or another connected provider.
A later provider refresh or sync can replace local state when the source provider still reports different IDs.
Reset behaviour
Reset restores the fields in the editor to the values that were present when the detail panel was opened.
It does not undo an ID patch that has already been saved.
Where to fix an issue
The preferred fix depends on where the incorrect data originates.
Media server to tracker
For pairs such as Plex, Jellyfin, or Emby to Trakt:
Correct the match or metadata in the media server.
Refresh the item metadata when required.
Run the pair again.
Reopen Analyzer.
Confirm that the issue has disappeared.
Correcting the source is preferable to maintaining a local Analyzer patch.
Tracker to media server
When the tracker is the source:
Verify the item in the tracker.
Remove an incorrect or duplicate tracker item when necessary.
Confirm that the destination can resolve the media.
Run the pair again.
Analyzer does not directly edit tracker data.
Local state only
Use Edit Manual IDs when:
You need to confirm that stronger IDs resolve the issue
The provider temporarily reports incomplete IDs
You are diagnosing a local state mismatch
After testing, correct the metadata at the source so the fix survives future state refreshes.
Recommended workflow
Analyze button
Select Analyze to rerun the current comparison.
Analyzer refreshes:
Active pair routes
Missing peer problems
Manual block state
System findings
Scope exclusions
Provider limit information
The current search and selected view remain available where possible.
Analyzer requests can run for up to 120 seconds before the interface aborts them.
Performance and pagination
Analyzer separates issue results from the complete state browser.
Needs attention loads the current issue set and displays it in pages.
All scoped items requests provider state pages from the server.
The page size is 250 items.
Large installations should select only the pairs required for the investigation.
This reduces analysis scope and makes the result easier to interpret.
Troubleshooting
No scoped state yet
Run the selected pair and reopen Analyzer.
Confirm that the pair and required feature are enabled.
Scoped is higher than expected
Check:
Selected pairs
Pair direction
Two-way mode
Enabled features
Pair media type settings
Switch to one affected pair during troubleshooting.
Visible is lower than expected
Clear the search field.
Check the current page and selected view.
Visible only counts rows displayed on the current page after filtering.
An item is not listed under Needs attention
Open All scoped items and search for it.
The item may be healthy, blocked, excluded by pair settings, or outside the selected routes.
Blocked count is unexpected
Open Editor and review manual blocks for the affected provider and feature.
Analyzer loads manual block rules from local Editor state.
IDs disappear after saving
The source provider may still report the old identifiers.
Correct the metadata at the provider and rerun the pair.
Manual ID changes affect local runtime state and are not written back to the provider.
No reason is displayed
Not every missing peer result includes a detailed destination message.
Review the item IDs, System findings, provider logs, and pair configuration.
The same issue returns after sync
The underlying source metadata, provider limit, manual rule, or pair scope is still unchanged.
Fix the original cause rather than repeatedly patching local IDs.
Analyzer reports no issues but sync still looks wrong
Check:
The correct pair is selected
The feature is enabled
The expected direction is active
The item is not excluded by type settings
The item is not manually blocked
The sync run completed successfully
Then inspect System findings and the Output panel.
Use Events to review what happened during the affected sync.
Analysis fails or times out
Reduce the selected pair scope and run Analyzer again.
Check the Output panel for provider, state, or metadata errors.
UI reference
View selector
Switches between:
Needs attention
All scoped items
Sync pairs
Selects the routes included in the comparison.
Analysis status
Displays:
Issues
System findings
Blocked items
Provider item counts
Analyze
Reruns the current analysis.
Search
Filters the current result page.
Show IDs
Shows or hides item identifiers.
Result table
Displays provider, feature, title, and media type.
Detail panel
Displays item status, IDs, reasons, exclusions, limits, and diagnostics.
Resizable divider
Changes the height of the result and detail panels.
Related topics
Last updated
Was this helpful?