Indexers

Indexers is where you connect Scryer to your indexers — each entry is a Scryer-side configured provider instance for an indexer integration.

Plugin-backed provider

entries are configured provider instances. The available fields come from the installed plugin and its provider catalog metadata. This page covers what Scryer needs to store and test for the configured connection.

• To access: Settings → Indexers
• To view: Requires manageSystemSettings app permission

Working In Indexers

If searches aren’t returning results, check that the indexer instance here is enabled and that the connection fields are correct before adjusting routing or rules.

If you just installed an indexer plugin, create the provider instance here before assigning it in facet Routing settings — routing can only reference instances that already exist.

To add an indexer, choose an installed provider type, enter the connection fields that provider requires, and test or validate the connection when the UI exposes that action. You can also edit, disable, or remove existing instances. Name instances by environment or policy, and keep those names stable, so facet routing pages remain clear over time.

The usual order is: install or update the required plugin, then create the configured provider instance here. Disable an instance before removing it from routing rules, and after editing one, validate a single controlled workflow to confirm routing still points at the intended connection.

Related Concepts

• Plugins — where the indexer provider plugin must be installed before an instance can be created here
• Rules — conditions that route release searches to specific indexer instances
• Movie Routing Settings — where configured indexer instances are assigned to Movie library operations
• Wanted Items — monitored titles that trigger indexer searches when Scryer looks for missing or below-cutoff files