You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried downgrading to find version that can be used as a workaround
The problem
Hello,
I am using PlexTrakSync in a docker container and only in watch (Scrobbler)
When I rewatch an episode I get the following error: Conflict - resource already created
Please see below my config.yaml
watch:
add_collection: false
remove_collection: false
# what video watched percentage (0 to 100) triggers the watched status
scrobble_threshold: 90
# true to scrobble only what's watched by you, false for all your PMS users
username_filter: true
# Show the progress bar of played media in terminal
media_progressbar: true
# Clients to ignore when listening Play events
ignore_clients: ~
Is there an actual problem? the conflict error can be ignored as it will scribble with next tick. the conflict can happen if you run watch command multiple times for same trakt.tv account.
You are right. I just tried again and rewatches are added fine.
I had only one instance of watch running. Maybe while I was testing the rewatches were close to each other? I was fast forwarding the same episode to check if it will be registered.
Confirmation
The problem
Hello,
I am using PlexTrakSync in a docker container and only in watch (Scrobbler)
When I rewatch an episode I get the following error: Conflict - resource already created
Please see below my config.yaml
and my container .yaml
Steps to reproduce the behavior
Error trace / logs
Expected behavior
From what I read, scrobbler should mark as watched when you are re-watching something.
I found this pr that maybe is relevant ? #1882
Inspect of problematic items
No response
Workarounds
No response
Config file contents
No response
Install method
docker-compose
Version
0.30.10
Python Version
3.12.3
Plex Server Version
1.40.3.8502
Operating System and Version
Debian 12 (Open Media Vault 7.1.1-1)
The text was updated successfully, but these errors were encountered: