Reject duplicate plays to history
I don't do regular housekeeping of my trakt data and things are prone to get messy due to various bugs in apps and plugins but I'll always end up with duplicate plays at some point. Many of those end up going from check-ins to plays at the same timestamp which shouldn't get accepted as valid by the site at all imho or at least end up getting merged. Despite not not being advertised outside of some support threads and a single kodi forum thread I end up getting a lot of visitors on my duplicate removal script (500+ last year) which tells me this is quite a common issue and affects plenty of people :/...
Actually just happened again. Probably going to turn on debug logging 24/7 again... Going to have to look at the script once I have the motivation but how likely is it that the response from trakt is not sending all data and that is why it sends them all again (or is the response code gospel)?
Do you mean the generation of the duplicates? When manually doing stuff I only get additional plays but never duplicates. What I am referring to is additional plays at the exact same timestamp generated from syncs from various media center plugins or mobile apps. I only occasionally try a mobile app so my main contender in my case would be the Kodi plugin (last time I cleaned up I had tripple plays for most :/).
So is this limited to manual play adds? I don’t use a hyper-manual approach like some so am curious.
I haven’t had any problems with duplicates, even when I expect them.
Or is this always/often happening when you check in at the same time as starting a new play???
I’m new-ish to Trakt (at least VIP/using my account actively), so I don’t think I’ve used the “Check In” function more than once or twice.
So if someone had an answer to especially my last question, it would be a big help. Thanks.
AdminJustin Nemeth (Founder, trakt) commented
Scrobbles have a check to make sure the same data isn't inserted multiple times. I'll need to look into this for the manual watched history sync. It is not quite that simple since adding more lookups for every play will add a lot of performance overhead. This is likely a Trakt API v3 type of thing.