Analyzer

Find items that didn’t sync and identify missing IDs or mismatches.

Analyzer helps you answer one question:

Why didn’t this item sync?

It reads your local runtime state and flags missing matches and bad IDs. It points you to where to fix the problem, usually in your media server metadata.

What it does

• Reads state.json from your latest runs.

• Uses enabled pairs to detect real gaps.

• Flags common issue types (missing peers, missing IDs, invalid IDs).

• Suggests ID fixes (best effort).

Analyzer does not “fix metadata for you”. It helps you find the right fix faster.

What you need

• At least one recent sync run (so state.json exists).

• The pair and feature must be enabled.

Optional, for better suggestions:

• TMDb key (see Metadata)

• Trakt app credentials (if you use Trakt lookups)

Workflow

1

Run a sync first

Analyzer works from runtime state. Do one normal sync run before you start debugging.

2

Filter down to the failing pair

Use the pair chips to focus on one pair. Start with the pair you care about right now.

3

Focus on issues

Use Scope: issues first. Work through missing_peer items before anything else.

4

Fix at the source, then re-run

For media-server → tracker pairs:

1. Fix IDs in Plex/Jellyfin/Emby (match, refresh metadata, correct year).

2. Re-run the pair.

3. Confirm the issue disappears.

Where to fix issues

In almost all setups, fix the source of the pair.

Media server → tracker:

• Fix IDs and matching in Plex/Jellyfin/Emby.

• Re-run the pair.

Tracker-only items:

• Analyzer does not edit trackers directly.

• Clean it up in the tracker, or import it to your media server.

Issue types (reference)

Common issue types

• missing_peer: item exists on source, but no match exists on the target for this pair.

• missing_ids: core IDs (IMDb/TMDb/TVDb) are missing.

• invalid_id_format: ID format is wrong (example: IMDb missing tt).

• key_missing_ids: key claims an ID, but the ID field is empty.

• key_ids_mismatch: key says one ID, field says another.

Suggestions are hints, not guarantees. Sanity-check before trusting them.

UI guide (quick)

• Pair chips: focus on a single pair.

• Scope:

  • issues: show only missing peers for active pairs.

  • all: show everything relevant to the active pairs.

• Grid: sort and search by provider, feature, title, year, type.

• Detail panel: shows likely cause and suggestions.

• Manual IDs: lets you test IDs locally and re-run planning.

Related: Editor.

Screenshots

Analyzer – top controls

Analyzer – grid

Analyzer – detail panel

Analyzer – manual IDs editor

Troubleshooting

• Issue count looks too high: check which pairs/features are enabled.

• No suggestions: add TMDb metadata, or connect Trakt for richer lookups.

• Same issue returns after sync: source metadata is still wrong. Fix IDs/year and re-run.