-
- plexId: 160383
result: true
sectionResults:
- id: 0
result: true
ruleResults:
- operator: OR
action: equals
firstValueName: Overseerr - Requested in Overseerr
firstValue: 1
secondValueName: boolean
secondValue: 1
result: true
- operator: AND
action: before
firstValueName: Plex - Newest episode view date
firstValue: 2023-11-24T22:38:27.000Z
secondValueName: custom_days
secondValue: 2024-03-09T02:49:28.457Z
result: true
- operator: AND
action: not_equals
firstValueName: Overseerr - Requested by user (Plex or local username)
firstValue:
- user1
secondValueName: text
secondValue: myuser
result: true
- id: 1
result: false
operator: OR
ruleResults:
- operator: OR
action: equals
firstValueName: Plex - Amount of watched episodes
firstValue: 8
secondValueName: number
secondValue: 0
result: false
- id: 2
result: false
operator: OR
ruleResults:
- operator: OR
action: equals
firstValueName: Overseerr - Requested in Overseerr
firstValue: 1
secondValueName: boolean
secondValue: 1
result: true
- operator: AND
action: contains
firstValueName: Plex - [list] Users that saw all available episodes
firstValue:
- myuser
- user2
secondValueName: Overseerr - Requested by user (Plex or local username)
secondValue:
- user1
result: false From my (very poor) understanding, the This is a slightly modified example of the community rule "Seen by Overseer requester & older than 30 days OR not watched by requester and older than 90 days". There are 3 users in play here: I would have thought that in: - operator: AND
action: contains
firstValueName: Plex - [list] Users that saw all available episodes
firstValue:
- myuser
- user2 It wouldn't trigger adding to the collection until user1 had finished watching all episodes. Full export: mediaType: SHOWS
rules:
- "0":
- firstValue: Overseerr.isRequested
action: EQUALS
customValue:
type: boolean
value: "true"
- operator: AND
firstValue: Plex.sw_lastWatched
action: BEFORE
customValue:
type: custom_days
value: "30"
- operator: AND
firstValue: Overseerr.addUser
action: NOT_EQUALS
customValue:
type: text
value: myuser
- "1":
- operator: OR
firstValue: Plex.sw_viewedEpisodes
action: EQUALS
customValue:
type: number
value: 0
- operator: AND
firstValue: Plex.sw_lastEpisodeAddedAt
action: BEFORE
customValue:
type: custom_days
value: "30"
- operator: AND
firstValue: Overseerr.isRequested
action: EQUALS
customValue:
type: boolean
value: "true"
- operator: AND
firstValue: Overseerr.addUser
action: NOT_EQUALS
customValue:
type: text
value: myuser
- "2":
- operator: OR
firstValue: Overseerr.isRequested
action: EQUALS
customValue:
type: boolean
value: "true"
- operator: AND
firstValue: Plex.sw_allEpisodesSeenBy
action: CONTAINS
lastValue: Overseerr.addUser
- operator: AND
firstValue: Overseerr.addUser
action: NOT_EQUALS
customValue:
type: text
value: myuser This instance is connected to all services (Plex, Overseer, Radarr and Sonarr). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey, it matches your first section, that’s why the media item was added. If the other sections were ‘AND’ sections, they would block it. But since they are ‘OR’, just matching the first section is enough. |
Beta Was this translation helpful? Give feedback.
Hey,
it matches your first section, that’s why the media item was added. If the other sections were ‘AND’ sections, they would block it. But since they are ‘OR’, just matching the first section is enough.