Matching "Specials" Seasons - Filters | field > conditions > name > exclude: specials

[infiniterookie]

I might be missing something or possibly Redirecter does not support this function, but when I try to leverage the filters to match requests for "Specials" seasons, it does not.

My filter is configured to look for, conditions: name: exclude: specials thinking it would match any requests for Seasons that are "Specials" as seen in the below snippet.

Webhook output from log (see section for name):

  "seasons": [
    {
      "airDate": "[REDACTED]",
      "episodeCount": [REDACTED],
      "id": [REDACTED],
      "name": "Specials",
      "overview": "",
      "seasonNumber": 0,
      "posterPath": "[REDACTED]"
    },

Filter configuration in config.yaml:

    - media_type: tv
      is_4k: false
      conditions:
          keywords:
              exclude: anime
          name:
              exclude: specials
      apply: Sonarr

Filter processing from log:

2025-09-17 13:26:53 [DEBUG]: Filter check for keywords did not match.
2025-09-17 13:26:53 [DEBUG]: Filter check:
Field: keywords
Filter value: exclude: anime
Request value: Keywords array (matched)
2025-09-17 13:26:53 [DEBUG]: Filter check:
Field: name
Filter value: exclude: specials
Request value: [REDACTED]
2025-09-17 13:26:53 [INFO]: Found matching filter at index 4
2025-09-17 13:26:53 [DEBUG]: Sending configuration to instance:
instance: Sonarr
postData: mediaType: tv, seasons: [0], rootFolder: [REDACTED], serverId: 0
2025-09-17 13:26:54 [INFO]: Configuration applied to request ID 28
2025-09-17 13:26:54 [INFO]: Configuration applied for request ID 28 on instance "Sonarr"
2025-09-17 13:26:54 [INFO]: Request ID 28 approved successfully
2025-09-17 13:26:54 [INFO]: Request ID 28 approved for instance "Sonarr"
2025-09-17 13:26:54 [INFO]: Request processed and sent to instances

[varthe]

Sorry for the late response life got in the way.

Right now it looks for the first field named "name". Specials is nested deeper in the JSON so it's not possible to do this.
I'm cooking up v3 at the moment with a bunch of other fixes so I'll try to implement a way to target specials as well.

[infiniterookie]

No worries. I'm behind on replying to your reply too.

Happy to hear you'll consider looking into this. Thank you!

FWIW, I was able to work around the issue by switching to the Jellyseerr develop branch where it's possible to disable Specials as an option.

That project will be merging that function into their main branch with the launch of the new Seerr project.

So this might become more of an edge case scenario for situations where someone wants to be able to review requests whenever Specials are selected (when enabled in Seerr).