Tested with 184.108.40.206 yesterday and the issue is not reproduced that often I only been able to reproduce twice on web by clicking and changing the tv episode more than 80 times.
I have observed that the error appeared when the load is higher on the server and the sqlite3 is stressed on updating things for example I had a sys load average of 3.5 at 5 min by that time and the Emby response time between 0.8s to 1.4s. HDD IO was around 140MB/s out of 2000MB/s due to transcoding etc. I was thinking about if it will not be a good idea to keep the transcoding folder outside Emby, even that I have 550k IOPS I think delays are triggered on sqlite. I can add an extra hdd with slower performance something about 1500MB/s with 250k IOPS just for Emby meta and db.
I think sometimes when you are at the end of a tv episode and you press start next, something somewhere is not changed fast enough on the server side and that's why this error is triggered.
@ray-finkle are you experiencing this when your sys load is increased or all the time?
@Luke let me know if I can help with something else.