8000 Plex api communication failure when attempting to run rules · Issue #1747 · jorenn92/Maintainerr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Plex api communication failure when attempting to run rules #1747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
drlambnz opened this issue Apr 28, 2025 · 2 comments
Open

Plex api communication failure when attempting to run rules #1747

drlambnz opened this issue Apr 28, 2025 · 2 comments
Labels
stale When something hasn't had any activity in a while.

Comments

@drlambnz
Copy link

Describe the bug
When attempting to run rules in Maintainerr, the a set of rules fails to run, indicating a "Plex api Communication Failure". Other rule sets and collections work as normal against the same Plex instance, just this one rule set/collection is failing.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Rules'
  2. Click on 'Run Rules'
  3. Allow Rules to process. Check debug log for Plex API Communication Failure against this ruleset.

Expected behavior
Expecting the ruleset to process, to allow for the collection to update with the new ruleset

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

  • OS: Windows 11 23H2 22631.5189
  • Docker Container

Additional context
Errors in the Debug Log show as below:
[maintainerr] | 28/04/2025 13:11:00 [INFO] [RuleExecutorService] Executing rules for 'Shows Leaving Soon' [maintainerr] | 28/04/2025 13:12:59 [WARN] [PlexApiService] Plex api communication failure.. Is the application running? [maintainerr] | 28/04/2025 13:12:59 [DEBUG] [PlexApiService] fetch failed [maintainerr] | 28/04/2025 13:20:30 [INFO] [RuleExecutorService] Execution of rules for 'Shows Leaving Soon' done.

Rules for this Ruleset as below:
`mediaType: SHOWS
rules:

  • "0":
    • firstValue: Plex.addDate
      action: BEFORE
      customValue:
      type: custom_days
      value: "1460"
  • "1":
    • operator: AND
      firstValue: Plex.labels
      action: NOT_CONTAINS
      customValue:
      type: text
      value: Keep
  • "2":
    • operator: AND
      firstValue: Plex.sw_amountOfViews
      action: EQUALS
      customValue:
      type: number
      value: 0
    • operator: OR
      firstValue: Plex.lastViewedAt
      action: BEFORE
      customValue:
      type: custom_days
      value: "1460"
      `
@benscobie
Copy link
Collaborator
benscobie commented Apr 28, 2025 •
edited
Loading

This is not a failure per say, it is a warning that a specific Plex API call failed, processing still completed. This is likely happening when fetching data for one of your rules, and isolated to a single item in that library as there's only 1 log line. Our logging for Plex interactions needs updating to include some more detail to help identification. In the mean time, it would be worth taking a look at your Plex Server logs for any errors if this happens persistently.

@github-actions GitHub Actions
Copy link
Contributor

This issue has been marked stale because it has been 30 days with no activity.

@github-actions github-actions bot added the stale When something hasn't had any activity in a while. label May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale When something hasn't had any activity in a while.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@benscobie @drlambnz
0