Huntarr v9.2.0: Release Information
1. The Core Architecture Shift: True Instance Independence
The Change:
We have fundamentally rewritten the background cycle management. In previous versions, instances were effectively tied to a single processing loop. This meant they didn't fully respect per-instance sleep times and often ran simply because the loop was cycling, or got stuck waiting for other instances.
How it works now:
Each App Instance is now scheduled on its own unique interval. The main system loop now only triggers an instance if its specific next_cycle_time has arrived. If no instances are due, the system sleeps until the soonest scheduled run.
Why this matters (The "Big Change"):
- True Independence: Your "4K Radarr" instance and your "Anime Sonarr" instance now run completely separately. One busy instance will no longer hold up the others.
- Respects Configuration: If you set an instance to sleep for 60 minutes, it will actually sleep for 60 minutes.
- Upgrade Note: When you upgrade, you may notice a change in rhythm. Instances will now execute strictly when due, rather than constantly cycling in a loop.
2. Identity & Persistence (Instance IDs)
The Problem:
Previously, Huntarr identified instances by their display name. If you renamed an instance (e.g., changing "Sonarr" to "Sonarr 4K"), Huntarr treated it as a brand-new instance. This caused users to lose their processed items list, cycle history, and countdown timers.
The Solution:
We have introduced Persistent Instance IDs. Every instance is now assigned a stable, unique identifier in the database that never changes.
The Benefit:
- Rename Freely: You can now rename instances as often as you like without breaking anything.
- Data Safety: Your history, "processed" cache, and configuration stay intact regardless of name changes.
- Docker Persistence: We now save countdown timers to the database. If you restart your Huntarr Docker container, your timers won't reset to zero; they will pick up exactly where they left off.
3. Granular Control: Tagging System
The Change:
We have removed the "Mass Toggle" for tagging and replaced it with three individual toggles.
New Options:
You can now independently enable/disable tags for:
- Missing
- Upgrades
- Shows Missing
⚠️ Important for Upgraders:
By default, all three toggles will be ON after the update. If you previously had the mass toggle turned off, you must go into your instance settings and manually turn these off to match your previous preference.
4. Swaparr Intelligence Upgrades
Strike System Fix (Issue #687):
Previously, Swaparr might strike a download for "No Progress" or "ETA Too Long" too early.
- New Logic: Strikes now only apply if the download has been running longer than the configured Max Download Time. This prevents false positives on large files that are just starting up.
Manual Import Protection (Issue #706):
We found that some downloads were hitting 100% completion but getting stuck in the queue because they needed manual import (e.g., due to a naming mismatch). Swaparr would incorrectly view these as "stalled" and remove them.
- New Setting: "Remove completed (100%) stalled" (Default: ON).
- How to use: Turn this OFF if you want Huntarr to ignore 100% completed downloads, allowing you time to manually import them without fear of deletion.
5. Resource Management: Max Seed Queue
The Feature:
For users running Torrents, we have added a Max Active Seeds limit per instance.
How it works:
You can set a threshold (e.g., "50 active seeds"). Before running a cycle, Huntarr checks your client (qBittorrent or Transmission).
- If Seeds >= Limit: The cycle is skipped entirely.
- If Seeds < Limit: The cycle proceeds as normal.
- Why? This prevents Huntarr from adding more torrents to a client that is already overwhelmed or hitting tracker limits.
HomePage
Instance Identifier
Tags Rewritten
Max Seed Queue
