Hi!
I've been testing scrobbling to WeTrakr from Plex using Crosswatch and wanted to share some feedback regarding an edge case during binge-watching.
The Situation
When playing series on Plex with Autoplay enabled, Plex often chains consecutive episodes without sending a clean stop playback event. It moves directly from progress >= 95% on Episode 1 to progress = 1% on Episode 2 within the same session.
Because client scrobblers sometimes fail to synthesize an explicit /scrobble/stop call during this rapid transition, WeTrakr only receives:
1. /scrobble/start and /scrobble/pause updates (which successfully report progress up to ~90-98%).
2. Followed immediately by a new /scrobble/start for the next episode.
Since WeTrakr strictly waits for a /scrobble/stop call to persist the item into the user's watched history (`/sync/tracking/watched/history/episodes`), the episode ends up stuck in limbo and is never marked as watched.
Suggestion
Have you considered implementing server-side auto-completion if a playback session reaches a high progress threshold?
For instance:
- If a session had previously reported progress >= 85% (or 90%), and the user starts a new playback session for a different item (or after a timeout), the backend could automatically finalize/commit the previous episode to the user's watch history.
Other platforms (like SIMKL) implement this fallback behavior, which makes scrobbling much more resilient against client players (Plex, Kodi, etc.) that drop stop events between consecutive episodes.
Thanks for the great work on WeTrakr!
