Movies passing the rules not being added to the Collection about maintainerr HOT 5 OPEN

Hey! It seems that the rule encountered an undefined statistics object, which is unexpected considering the object is initialized at the start. While it's possible that this issue could stem from a sluggish Plex server response, the error isn't what i'd expect in such scenarios.

API calls to Plex are configured with a timeout value of 5 seconds. If this limit is exceeded, the returned item is likely to be null. Although some calls are retried, not all Plex calls benefit from this mechanism. Maintainerr relies on an external library for Plex API communication, which currently lacks a built-in retry feature.

Is this the first time you encountered this issue? Does the problem resolve itself upon next rule executions?

from maintainerr.

Hi--

I've had the issue since 5/1/24 when you see from the screenshot that items were mysteriously removed but are still resolving as true when evaluated individually. The error I posted only occurs once. I have not been able to reproduce that error since the one occurrence.

To test, I restarted the Maintainerr container and manually ran the Movies Rules. I only see this in my logs, it's been 5 hours since I ran the rules manually:

[maintainerr] | 03/05/2024 16:34:54 [INFO] [NestApplication] Nest application successfully started [maintainerr] | 03/05/2024 16:35:11 [INFO] [RuleExecutorService] Starting Execution of all active rules [maintainerr] | 03/05/2024 16:35:11 [INFO] [RuleExecutorService] Executing rules for 'Movies Leaving Plex Soon' [maintainerr] | 03/05/2024 19:27:12 [WARN] [RadarrGetterService] [TMDb] Failed to fetch TMDb id for 'Bon Jovi Unplugged on VH1'

Is there any way I can increase the logging to see what's happening?

from maintainerr.

After another day, the movies returned to the Collection. The countdown dates are reset, but they are back. I'm fine with closing this, or I can provide some logs to help track down if there is a bug. Thanks again.

from maintainerr.

The only method to enhance logging is by enabling the 'DEBUG' flag in your Docker Compose/run command. However, I'm uncertain if this will provide additional information in this scenario.

If you encounter this issue again, it would be great if you were able to obtain some debug logs from Maintainerr and Plex's side. But it may not be straightforward to gather them when the problem doesn't happen consistently.

I'll leave this issue open for a few weeks. Please keep me informed if it reoccurs. Otherwise, I'll close it later.

Thank you for reporting this!

from maintainerr.

Hi there--

Sadly, the issue has reoccurred twice.

As you can see from the screenshot, all of the movies in my collection were removed. However, the movies that were removed were not processed (they had several days remaining), but are still passing the rule.

Here is my rules, it's fairly straightforward:

mediaType: MOVIES
rules:
  - "0":
      - firstValue: Plex.viewCount
        action: EQUALS
        customValue:
          type: number
          value: 0
      - operator: OR
        firstValue: Plex.lastViewedAt
        action: BEFORE
        customValue:
          type: custom_days
          value: "180"
  - "1":
      - operator: AND
        firstValue: Radarr.tags
        action: NOT_CONTAINS_PARTIAL
        customValue:
          type: text
          value: never_expire
  - "2":
      - operator: AND
        firstValue: Plex.addDate
        action: BEFORE
        customValue:
          type: custom_days
          value: "335"

Another odd thing -- My rules are set to process at 6am. Collections are set to 7am. Unless the timezone is off, it shouldn't be running at 3pm like the Logs say. I'm passing my timezone in through my docker-config like so:

   environment:
      - "PUID=${PUID}"
      - "PGID=${PGID}"
      - "TZ=${TZ}"
 

.env file:

TZ=America/New_York

from maintainerr.