Mark Played function not working.

[paul t 1]

Hello,

I'm having a frequent issue with several titles, where I can't mark it as played. In a browser when clicking "marked played" it flashes red, but then the tick is not selected and it is not marked as played/watched.

I've also tested on Android, Emby Theatre for Windows etc and it's the same result (except there the red tick isn't displayed at all in Emby Theatre). I'm running Emby in docker and have tested with the latest version 4.6.4.0 and still have this issue.

I checked the embyserver logs and I'm guessing this POST is the result of me clicking it and the response is a 200 OK, but nothing changes. (Tried with Debug logging but the output wasn't any more verbose than that below)

If I watch a film or show without pausing in between then it often is correctly marked as played automatically, but the manual function isn't working for me.

 

2021-07-25 11:43:04.984 Info Server: http/1.1 POST http://myembyserver:8096/emby/Users/0d019c9fc885423f99489b2127e1c57e/PlayedItems/46371?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox&X-Emby-Device-Id=be13434b-3920-4139-89b4-cbf47e7c6aa8&X-Emby-Client-Version=4.6.4.0. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0
2021-07-25 11:43:04.987 Info Server: http/1.1 Response 200 to 192.168.X.X. Time: 3ms. http://myembyserver:8096/emby/Users/0d019c9fc885423f99489b2127e1c57e/PlayedItems/46371?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox&X-Emby-Device-Id=be13434b-3920-4139-89b4-cbf47e7c6aa8&X-Emby-Client-Version=4.6.4.0

[Carlo 4561]

Hi, can you upload your complete server log so we can take a look at it?

[paul t 1]

Sure. Just so there was some recent activity I tried marking 4 or 5 titles as watched.

embyserver.txt

[Carlo 4561]

Hi if you go to the detail screen of a movie and click the watched button what happens?

[paul t 1]

Exactly the same unfortunately.

 

embyserver(1).txt

[Luke 42086]

Try refreshing the metadata on titles that are doing this, then try to mark played again and see if that helps. Thanks.

[paul t 1]

Thanks! That seems to resolve it.

[Luke 42086]

Thanks. The only known cause of this is due to having gone back and forth between them beta and stable channels at some point in the past, which is not supported.

[paul t 1]

OK I'll keep it in mind. I run it in a docker container and normally just do a fresh pull every few weeks, so wouldn't have expected that I switched channels (since it's the same tag). In any case, thanks for the quick and effective support.