Per-Instance Overrides lets you set different search behaviour for each Radarr or Sonarr instance independently, without changing your global settings.

---

If you run a single Radarr and a single Sonarr, your global settings cover everything and you don't need this feature. Per-Instance Overrides is for setups running multiple instances — a standard and a 4K Radarr, a main and an anime Sonarr, or any combination where different instances genuinely need different limits, cooldowns, or modes.

When overrides are off, every instance uses the global settings. When overrides are on, each instance can have its own values for specific fields. Instances without any overrides set continue to inherit global.

---

1. Open the Advanced tab
2. Toggle Per-Instance Overrides to on
3. An Overrides tab appears in the main navigation

---

Each instance can independently override any combination of these fields. Fields left unset inherit the global value.

Field	Applies to	Description
Cooldown Hours	Radarr + Sonarr	Minimum hours before re-searching the same item on this instance
Max Cutoff Unmet	Radarr + Sonarr	Maximum Cutoff Unmet items to search per sweep for this instance
Max Backlog	Radarr + Sonarr	Maximum backlog (missing) items to search per sweep for this instance
Max Missing Days	Radarr only	Minimum age (in days) a missing item must be before it is eligible for backlog search
Sample Mode	Radarr + Sonarr	Pick order for eligible items — see Sample Mode below
Backlog Enabled	Radarr + Sonarr	Enable or disable backlog nudges for this instance independently
Notifications Enabled	Radarr + Sonarr	Enable or disable sweep notifications for this instance independently

Note: Sonarr instances do not have a Max Missing Days field. That filter is Radarr-only.

---

Overrides use sparse storage — only fields you explicitly set are saved. The logic is straightforward:

• Any field you have not set on an instance inherits the global value for that field
• Any field you have set on an instance fully supersedes the global value for that field — there is no blending or averaging

For example: if your global cooldown is 48 hours and you set a cooldown override of 24 hours on your 4K Radarr, that instance uses 24 hours. Your other instances continue to use 48 hours. If you later change the global cooldown to 72 hours, your 4K Radarr still uses 24 hours — the override takes full precedence.

---

The Sample Mode field has an extra option not available in global settings: Use Global. Selecting Use Global means this instance defers to whatever the global Sample Mode is set to, including any future changes to it. This is the default state for any instance that has not had Sample Mode explicitly overridden.

---

With Per-Instance Overrides enabled, an Overrides tab appears in the main navigation alongside Instances and Sweep.

• The left rail lists all configured instances — click any to select it
• Each instance card shows the seven override fields
• Fields show their current override value, or a dimmed global-inherited placeholder if not set
• A Pending indicator appears on any card with unsaved changes
• Click Apply on a card to save that instance's overrides
• Reset All to Global clears all overrides for that instance — it inherits global on every field going forward

Note: Resetting clears the override values entirely. The values you had set are not remembered — if you reset and want to re-override, you start from scratch.

---

Rotate your device to landscape to access the Overrides UI on mobile. A third nav tab appears in the bottom rail alongside Instances and Sweep.

• The left rail lists all instances — tap to select
• Each field has stepper controls for quick adjustment
  • Cooldown Hours increments by 24
  • Max Cutoff Unmet and Max Backlog increment by 5
  • Max Missing Days increments by 7
  • Hold a stepper to accelerate
• Apply and Reset All to Global appear in the footer

---

In portrait mode, Per-Instance Overrides can be toggled on or off from the Settings tab. Full per-instance configuration requires landscape orientation.

---

By default, each instance inherits the global Notifications setting. If you enable Per-Instance Overrides and set Notifications Enabled on a specific instance, that instance's notification behaviour is fully independent — you can silence notifications for one instance while keeping them active for others, regardless of the global toggle.