Wanted

Wanted

The Wanted page (/wanted) is Sublarr’s queue of episodes and movies that don’t yet have subtitles in your target language. Items land here automatically — you rarely add anything by hand. Sublarr scans your library, decides what’s missing against your active Language Profile, and then either searches providers immediately or schedules the search based on your pacing settings.

Where wanted items come from

Sublarr discovers missing subtitles from any source you’ve connected:

• Sonarr / Radarr instances. Periodic syncs read every monitored series and movie, then check on disk whether the target-language sidecars are present.
• Standalone watched folders. Folders configured under Settings → Connections → Standalone are scanned on the same cadence and produce wanted items for matching files.
• Webhooks (push-driven). Sonarr / Radarr Download events arrive faster than the periodic scan and add wanted items for new releases the moment they hit the library.

The scan is incremental — only files modified since the last run are re-checked. Every sixth cycle a full scan re-validates everything to catch silent file moves and out-of-band deletions.

Status legend

Every row carries a status badge (left of the title). The colour scheme is consistent with the rest of the UI.

Status	Colour	Meaning
wanted	orange	Subtitle missing; queued for the next search cycle.
searching	blue (spinning)	Providers are being queried right now.
found	green	Subtitle downloaded and written to disk. Item disappears from the list shortly after.
extracted	teal	Subtitle came from an embedded video track, no provider needed.
failed	red	Search exhausted all eligible providers without a hit. The row keeps the last error tooltip on hover.
ignored	grey	You manually marked this item not interesting. Hidden from default views; show via the filter panel.
skipped	grey	The Wanted scanner’s eligibility filter excluded this item this cycle (e.g. slow-mode no_result cooldown, daily provider budget exhausted). Skipped items return to wanted automatically once the cooldown expires.

Manual versus automatic search

Sublarr searches automatically based on the Wanted Search scheduler job — interval and pacing live in Settings → System → Scheduler. Manual actions on the page take precedence and skip the queue:

• Search. Single-row button. Triggers an immediate provider sweep, bypassing eligibility cooldowns. Useful when a release just dropped and you don’t want to wait for the next tick.
• Process. Single-row. Searches and, if a result clears the score threshold, downloads it in one step.
• Batch Search. Toolbar button at the top. Runs Search on every row matching the current filter. Honours pacing and the per-provider rate limits — does not nuke your daily budget.
• Batch Translate. When the missing language has no provider hits, Sublarr can take the next-best embedded or sidecar track and translate it through the configured backend (Ollama, DeepL, …).
• Ignore / Un-ignore. Toggles the ignored status. Ignored items no longer count against your search quota.

The scanner state pill in the page header (scanning…, idle, N to search) reflects the global background queue, not the row you’re looking at. A spinning searching badge on a single row means that row’s manual search is in flight.

Filtering and grouping

The filter panel on the right narrows the list by:

• Status — any combination of the badges above.
• Language — wanted target language (e.g. show only items missing de).
• Source — Sonarr / Radarr / Standalone.
• Provider error — show only rows whose last failure was a specific provider (helps spot a single misbehaving adapter).

Episodes from the same series collapse into a grouped row by default — one row per Series · Season, with the badges aggregated. Expand a group to see individual episodes; the per-episode actions are identical to the flat-row view. Switch to flat layout via the toolbar toggle if you prefer scrolling over grouping.

Dry run — preview without writing

New in 1.10.0. A dry run executes the full pipeline for a batch of wanted items — profile gates, provider search, scoring, upgrade decision — but writes nothing to disk or to the database. You get, per item, the provider that would have won, the score, the format and the exact output path.

Use it to answer “what would automation actually do here?” before letting it run, or to confirm a scoring change had the effect you intended.

Result	Meaning
found	A candidate won. The provider, score, format and target path are shown.
not_found	The search ran and nothing cleared the bar.
skipped	A pre-flight gate stopped it — the reason is given (target already on disk, slow-mode backoff, and so on).
failed	The item could not be processed, e.g. the media file is missing.

Each item’s status is restored afterwards, so a preview never leaves rows stuck in “searching”. Up to ten items per run.

Note

A dry run deliberately records no decision log — persistence is part of what it suppresses. The result is shown inline instead.

Export

New in 1.10.0. Export downloads the current wanted list as CSV or JSON. The export follows the list as it is on screen, so filters apply.

Columns cover identity (title, season/episode, target language), state (status, existing subtitle, upgrade candidate, current score), and history (search count, last search, added date, last error) — enough to analyse a backlog in a spreadsheet or feed it into your own tooling.

Subtitle Automation interaction

When Subtitle Automation is on (Settings → Subtitle Automation), the Wanted scanner does more than just queue searches:

• Embedded tracks are extracted into sidecars before any provider call, so embedded German lines never trigger a paid translation.
• Foreign-track cleanup (per-series override or global toggle) runs during the same scan and deletes off-target sidecars left by the scene group.
• SDH source tolerance lets the scanner accept SDH-stripped variants when the regular variant doesn’t exist.

Each of those is documented in detail under Settings → Subtitle Automation.

Common questions

Why does an item flip back to wanted after I ran Search? The search returned no result that cleared the score threshold. Lower the threshold per language (Settings → Translation / Profiles) or pick a different provider order.

Why is Search greyed out? The row is already searching — wait for the spinner to clear. Failures auto-clear after the configured cooldown.

Where’s the search history? Per-item history lives behind the ⋯ dropdown on each row → History. Global activity (every search, download, translate, post-process) is on the Activity page.