Setting up rules (that seem logical) but they don't work?

[Dental1347]

Hi,

First up, thanks for the amazing program! It looks slick, and connecting the different services was a breeze (radarr v5, sonarr v4, plex and overseerr)!

I have run into an issue however. I made myself a script were irregular series are tagged with the irregular tag. (e.g., s1 3 4 = irregular, s1 2 3 = regular)

I have made the following rule to flag these series for deletion:

The idea is simple:

• Have series flagged which have the irregular tag, (external script), they are to be removed after 30 days + the last episode needs to be watched by the person who requested it.

I know this is possible, but the screenshot above should flag them as well (it doesn't when I run the rule)

What am I doing wrong here?

[jorenn92]

Hi,

thanks for trying Maintainerr, i’m happy you got it working smoothly!

There are 2 potential reasons that could explain this behavior:

• Tags are case-sensitive. Does your ‘irregular’ tag’s case in Sonarr match the value in the rule field 100%?
• When a show has multiple tags, Sonarr will return a list and ‘equals’ won’t work anymore. It’s better to use ‘contains’, this should work for both lists and text.

If the above doesn’t fix your issue, is there anything in the logs that might help?

[Dental1347]

Thanks,

The first point is not the case, I checked this.
The second point, however, is the culprit here!

[Dental1347]

Another question on this. I have set a timer where the last episode must have been seen BEFORE 30 days. Effectively I'm trying to say that it should only be flagged when the last episode has been 30 days ago, and ideally by the person who has requested it.

How would I go about that?
Something along the lines or plex user > equals > ogerserrr request user?

The idea here is to clean up irregular series with:

• that have been watched,
• are 30 days inactive after the last episode has been watched,
• and the last watch was by the person who requested it,
• OR 90 days overall inactivity across the board.

With this, if a series is watched when it is already flagged, will maintainerr remove the series from the collection?

[jorenn92]

Thanks,

The first point is not the case, I checked this. The second point, however, is the culprit here!

Great news! I’ll clarify this in the documentation.

[jorenn92]

Another question on this. I have set a timer where the last episode must have been seen BEFORE 30 days. Effectively I'm trying to say that it should only be flagged when the last episode has been 30 days ago, and ideally by the person who has requested it.

How would I go about that? Something along the lines or plex user > equals > ogerserrr request user?

The idea here is to clean up irregular series with:

* that have been watched,

* are 30 days inactive after the last episode has been watched,

* and the last watch was by the person who requested it,

* OR 90 days overall inactivity across the board.

With this, if a series is watched when it is already flagged, will maintainerr remove the series from the collection?

Hi,

I can't verify the rule right now, but I believe it should be something along these lines.

This isn't perfectly what you requested, as it's not possible to only get the last person who watched an episode of a show. But it is possible to get a list of people who watched episodes of a show.

• Section 1
  • rule 1
    • Plex total views BIGGER than 0
    • AND Plex last episode seen at BEFORE amount of days 30 (Or 'plex last viewed at' if you rather want the last watch date across all episodes)
    • AND Plex users that watch the show CONTAINS Overseerr requested by user
• Section 2
  • Rule 1
    • OR Plex Last viewed at BEFORE 'amount of days' 90

Hopefully this pushes you in the right direction.

[jorenn92]

With this, if a series is watched when it is already flagged, will maintainerr remove the series from the collection?

The next time the rule runs and a show doesn't meet the criteria anymore (because someone watched it), it will be removed from the collection.

[Dental1347]

@jorenn92

To follow up on what I ended up doing:

Section #1

Rule #1
First value: Plex - Amount of watched episodes
Action EQUALS
Second value Plex- Amount of available episodes

Rule #2
Operator: AND
First value: Plex - Last episode seen at
Action: BEFORE
Second value: Amount of days
Custom value: 30

Rule #3
Operator: AND
First value: Plex - Users that saw all available episodes
Action: CONTAINS
Second value: Overseerr - Requested by user (username)

Section #2

Rule #1
Operator: OR
First value: Plex - Last viewed at
Action: BEFORE
Second value: Amount of Days
Custom value: 60

Section #3

Rule #1
Operator: AND
First value: Sonarr - Tags
Action: CONTAINS
Second value: Text
Custom value: irregular

It seems to work, what do you think of this one?

[Dental1347]

I noticed that Plex - Last episode seen at, behaved differently than I expected. I figured it was the last episode within the series, but it seems to be just the last episode the user watched, which wasn't what I was searching for. I hope to have solved this issue with Section 1, Rule 1.

[jorenn92]

Yeah they are a bit confusing. They're supposed to be a bit different.

I'll try to explain with an example:

If user 1 watched episode 5 3 days ago, and user 2 watched episode 3 1 day ago, 'Last episode seen at' should return the first watch of user 1, because it's a newer episode.

'Last viewed at' doesn't look at episode number and just returns the latest watched episode, so this should return the latter in my example (user 2's view)

However, i noticed that the sorting of ' Last episode seen at' is broken at the moment, and they currently just do the same thing..
A fix will be available in the next release.

[appiekap653]

@jorenn92

To follow up on what I ended up doing:

Section #1

Rule #1 First value: Plex - Amount of watched episodes Action EQUALS Second value Plex- Amount of available episodes

If someone watches an episode two times, for example the first half on day 1, and the remaining half on day 2.
Would this number still equal or will it get higher then available episodes?

Rule #1 Operator: AND First value: Sonarr - Tags Action: CONTAINS Second value: Text Custom value: irregular

Will this last AND section compare itself to both OR sections? or do you need to copy this one in both the OR sections?
Is it (Section 1 and Section 3) or (Section 2 and Section 3), or is it Section 1 or (Section 2 and Section 3)?

[jorenn92]

If someone watches an episode two times, for example the first half on day 1, and the remaining half on day 2. Would this number still equal or will it get higher then available episodes?

'Plex - Amount of watched episodes' will essentially fetch the same value as doing this action on Plex's UI: click on the 3 dots next to your movie/show (or season/episode) and choose 'View play history'

I believe this will only include complete views. So in your example, it would count as 1 view. But do correct me if I'm wrong.

FYI, Issue #466 is related to this. Another user noticed that media manually flagged as 'watched' won't count as a play.

Rule #1 Operator: AND First value: Sonarr - Tags Action: CONTAINS Second value: Text Custom value: irregular

Will this last AND section compare itself to both OR sections? or do you need to copy this one in both the OR sections?
Is it (Section 1 and Section 3) or (Section 2 and Section 3), or is it Section 1 or (Section 2 and Section 3)?

Sections will always be executed against the previous section result. So in this case, it would be represented by: [[Section 1 OR Section 2] AND Section 3]