Adding tags to existing apps/indexers does not remove the indexers from the apps #709

New issue

Closed

opened 2026-02-20 10:02:33 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 10:02:33 -05:00

Owner

Originally created by @trentks on GitHub (Nov 30, 2022).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

If you already have existing indexers in prowlarr that are synced across to apps, then you add tags to the indexers/apps in prowlarr to try to trim what indexers are available to certain apps, the indexers are not removed from the apps.

Expected Behavior

The wiki states "Only in instances where an App and Indexer have matching tags or no tags at all will an indexer be synced to an app". I would expect that if there's not a tag match (and tags exist), that the indexer is not available to the app (i.e. is removed).

Steps To Reproduce

Note what apps have what indexers available
Add tags to existing apps and indexers in prowlarr, to attempt to limit the indexers available to each app
Have existing apps all be on "Full sync" mode
Run an "Application Indexer Sync" task
Check apps to see what indexers they have available, it will be identical to what was available in step 1.

Environment

- OS: Manjaro Linux
- Prowlarr: 0.4.9.2083 (via the aur)
- Docker Install: No (native systemd service)
- Using Reverse Proxy: No
- Browser: Firefox 107.0

What branch are you running?

Master

Trace Logs?

Indexers on prowlarr:

Apps in prowlarr (no convenient way to show what tags each app has, but believe me when I say that the lidarr app has the lidarr tag, the sonarr app has the sonarr tag, etc):

Trace log after turning on trace logging, deleting logs, and running the "Application Indexer Sync" task:
prowlarr_trace_log.txt

As an example, this is lidarr's indexers after having run the application indexer sync:

All existing indexers are still in place (on all of lidarr, sonarr, radarr, and the two readarr instances).

This was discussed with/discovered in conjunction with @bakerboy448 on discord.

AB#4243

Originally created by @trentks on GitHub (Nov 30, 2022). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior If you already have existing indexers in prowlarr that are synced across to apps, then you add tags to the indexers/apps in prowlarr to try to trim what indexers are available to certain apps, the indexers are not removed from the apps. ### Expected Behavior The wiki states "Only in instances where an App and Indexer have matching tags or no tags at all will an indexer be synced to an app". I would expect that if there's not a tag match (and tags exist), that the indexer is not available to the app (i.e. is removed). ### Steps To Reproduce 1. Note what apps have what indexers available 2. Add tags to existing apps and indexers in prowlarr, to attempt to limit the indexers available to each app 3. Have existing apps all be on "Full sync" mode 4. Run an "Application Indexer Sync" task 5. Check apps to see what indexers they have available, it will be identical to what was available in step 1. ### Environment ```markdown - OS: Manjaro Linux - Prowlarr: 0.4.9.2083 (via the aur) - Docker Install: No (native systemd service) - Using Reverse Proxy: No - Browser: Firefox 107.0 ``` ### What branch are you running? Master ### Trace Logs? Indexers on prowlarr: ![indexers](https://user-images.githubusercontent.com/23443021/204872328-53d4dea9-ad0e-4c4a-9c42-5ca2613d6a61.png) Apps in prowlarr (no convenient way to show what tags each app has, but believe me when I say that the lidarr app has the lidarr tag, the sonarr app has the sonarr tag, etc): ![apps](https://user-images.githubusercontent.com/23443021/204872346-b2a8fcc2-e966-4180-ab88-944ae54557cb.png) Trace log after turning on trace logging, deleting logs, and running the "Application Indexer Sync" task: [prowlarr_trace_log.txt](https://github.com/Prowlarr/Prowlarr/files/10125919/prowlarr_trace_log.txt) As an example, this is lidarr's indexers after having run the application indexer sync: ![lidarr_indexers](https://user-images.githubusercontent.com/23443021/204872349-3d7877cf-57e9-4986-a084-7f710d11f80a.png) All existing indexers are still in place (on all of lidarr, sonarr, radarr, and the two readarr instances). This was discussed with/discovered in conjunction with @bakerboy448 on discord. [AB#4243](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/4243)

deekerman

2026-02-20 10:02:33 -05:00

closed this issue
added the
Type: Bug

Status: In Progress
labels

deekerman commented

2026-02-20 10:02:35 -05:00

Author

Owner

@trentks commented on GitHub (Nov 30, 2022):

In addition, if you remove a tag from an existing indexer (desiring to no longer have it go to a particular app), then it is not removed from the app. This is again undesirable/unexpected behaviour in the wider-context. But within this context of knowing that apps aren't removed when there's a tag mismatch, it's not unexpected that this misbehaviour also exists.

@trentks commented on GitHub (Nov 30, 2022): In addition, if you remove a tag from an existing indexer (desiring to no longer have it go to a particular app), then it is not removed from the app. This is again undesirable/unexpected behaviour in the wider-context. But within *this* context of knowing that apps aren't removed when there's a tag mismatch, it's not unexpected that this misbehaviour also exists.

deekerman commented

2026-02-20 10:02:35 -05:00

Author

Owner

@psychonic commented on GitHub (Feb 12, 2023):

Thanks for the workaround of removing and re-adding the indexers. This issue was driving me crazy.

@psychonic commented on GitHub (Feb 12, 2023): Thanks for the workaround of removing and re-adding the indexers. This issue was driving me crazy.