Blocklist
Releases that Luminarr will never grab again, whether during automatic RSS sync or a manual search. The blocklist works at the release level — individual GUIDs, not whole movies.
What is the Blocklist?
Every release indexed from Torznab and Newznab feeds has a unique identifier — a GUID for NZBs and an infohash for torrents. The blocklist stores these identifiers. When Luminarr evaluates a release for grabbing, it checks the blocklist first. Any release whose GUID or infohash appears in the list is silently skipped.
This is distinct from the Import Exclusions list, which operates at the movie level. The blocklist operates at the individual release level — you can block a specific bad encode while still allowing Luminarr to grab a different release of the same movie.
Release-level blocking
Blocks a specific release by GUID or infohash. Other releases for the same movie are unaffected.
Applies everywhere
Checked during RSS sync, interactive search, and the queue's manual retry flow. No blocked release will ever be grabbed automatically.
Automatic and Manual Blocking
Failed imports
When a downloaded file fails to import — for example because it is password-protected, corrupted, or in an unexpected format — Luminarr adds the release to the blocklist automatically. This prevents the same bad file from being grabbed again on the next search cycle.
Automatic blocking only covers import failures. Download failures (client errors, incomplete downloads) are tracked in the queue but do not automatically add to the blocklist. You can block them manually.
Manual blocking from the queue
From the Queue page, you can blocklist any active or completed queue item. Use this when you can tell a release is bad before the import runs — for example, if the download was suspiciously fast or the release name looks wrong.
-
1
Open the Queue page
Find the release you want to block in the active queue or history.
-
2
Click the options menu
Select "Blocklist release" from the item's action menu. Optionally choose to also remove the download from the client.
-
3
Release is blocked and a new search begins
Luminarr adds the release to the blocklist, removes it from the queue, and immediately triggers a new search for the movie to find a better release.
GUID Checking
The blocklist check happens before any grab is sent to a download client, in both automatic and interactive flows.
If the GUID is found in the blocklist, the release is discarded and the next-best release is evaluated. No grab request is sent to the download client.
What is stored per entry
| Field | Description |
|---|---|
| GUID | The unique release identifier from the indexer (NZB GUID or torrent infohash) |
| Release Title | The original release name as returned by the indexer |
| Indexer | The indexer the release came from |
| Movie | The movie this release was matched to |
| Protocol | Torrent or Usenet |
| Blocked At | Timestamp when the entry was created |
| Reason | Why it was blocked: import_failed or manual |
Managing the Blocklist
The blocklist is available under Activity → Blocklist. Entries are sorted by date, newest first. You can filter by movie, indexer, or protocol.
Viewing entries
Each entry shows the release title, the movie it was associated with, the indexer it came from, and the reason it was blocked. This makes it easy to audit whether a block was expected or accidental.
Deleting individual entries
To unblock a specific release, click the delete button on its row. Once removed, the GUID is no longer checked and the release can be grabbed again if it appears in future searches.
Unblocking a release does not automatically grab it. You must trigger a new search from the movie detail page for Luminarr to find and grab the previously-blocked release.
Clearing the entire blocklist
A "Clear All" action removes every entry in the blocklist at once. Use this if you have made indexer or quality profile changes and want to allow all previously failed releases to be re-evaluated from scratch.
Clearing the blocklist is irreversible. All blocked releases will be eligible for re-grabbing on the next search. If those releases failed due to a persistent issue (e.g., a known bad release group), they will fail again.