Plex Scrobbler: 406 error when TV episode added to Plex collection

New VIP user, joined mainly to use the Plex scrobbler feature, yet for TV episodes only ‘now playing’ is being recognized by trakt. I’m using PMS for Windows, Version 1.24.5.5173 (latest available in the Public channel).
For the purposes of testing I acquired one episode of a show I have never watched before, added it to my Plex TV library (using Plex TV Series agent) and monitored the Plex console for trakt messages.

When the scanner updated the library, I got this in the console (I removed the 2 unique tokens):
Webhook: Error delivering payload to https://scrobblers.trakt.tv/plex/token1/token2: 406

When I started playing the episode, everything worked fine:
HTTP/2.0 (0.7s) 200 response from POST https://scrobblers.trakt.tv/plex/token1/token2

Not that it should matter, but the episode in question was: American Masters: Season 31 / 31x08 Edgar Allan Poe: Buried Alive. Tried with one other show, same issue.

For movies everything works as expected (both add to collection and play are properly recognized by trakt).
Sounds similar to issues reported in this thread: Trakt not using data from Plex Scrobbler which doesn’t seem to provide any resolution.

A 406 error means we ignore the web hook since it wasn’t movie or TV related. For example, if you were listening to music we’d ignore that.

Thanks, although I got that information from other threads already.

The thing is: with my testing I am monitoring PMS console and I’m 100% positive that the 406 response happens after a new TV show (with at least one episode) has been added to the TV shows library and the server is scanning that library. That suggests potentially one of the following issues (or a combination of both):

  • the payload that Plex sends contains some unexpected data (while that data still pertains to a TV show, not music etc.)
  • trakt.tv’s Plex scrobbler expects different data format / content than the one sent by Plex via web hook

I also noticed that there seems to be a difference in how Plex handles adding new TV shows vs adding episodes to ‘known’ shows:

  1. when adding a new show, the web hook is triggered during the library scan
  2. when adding an episode to an existing show, the web hook is triggered on library scan finish (the episode shows up in Plex library during the scan, but the web hook call is logged only after the scan is finished)

This leads me to believe that in the 1st scenario the payload has some content that trakt.tv cannot handle properly. Unfortunately I don’t know how to intercept that payload, although I might need to figure it out to confirm that this is the cause of the problem.

I enabled debugging for your account, so I’ll be able to see the web hook that Plex is sending. Please let me know when you’ve watched a new item that results in an error and I can see what the data looks like.

I ran couple of tests recently, I will provide screenshots with timestamps (CET timezone).

Test 1: added 3 episodes of ‘Wheel of Time’ TV series to the library, no previous episodes of the show existed in my library. 406 on the web hook.

Test 2: added 1 episode of Star Trek Discovery, no previous episodes of the show existed in my library. 406 on the web hook.

Test 3: added 1 episode of Curb Your Enthusiasm, couple of seasons/episodes in my library. 200 on the web hook.

Test 4: play/pause that newly added Star Trek Discovery episode, both worked as expected.

Ok, the 406 error on the first 2 was because Plex send a show level web hook without any episode info. Basically, if more then 1 episode is added to the collection, it sends a generic show event without any info on the specific episodes. I don’t know why Plex did that for only 1 episode of Star Trek: Discovery, that seems like another layer to the bug.

I posted this in August 2020, but it doesn’t appear Plex wants to fix the issue.

We need them to either send 1 web hook per episode (my preference) or include the episode details in the show level web hook.

Thank you for the explaination and following up on the issue on Plex forum. I’ll keep monitoring that thread, hopefully eventually it will get some attention.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.