Resume position can come from local player history, a profile or a service record. Different clients may store it differently. If a title resumes incorrectly, distinguish an outdated bookmark from a media-timing issue before clearing all history. First check which profile and edition are open, then correct only the affected history entry where supported. A remembered position can be valid for another viewer or a different cut, so a broad reset may hide the cause while discarding useful preferences.
Check the selected profile
Another viewer may have a different position. Look for the active household profile and whether another device last watched the same title under it. Shared profiles can overwrite each other's progress, and devices may synchronize at different times. Compare the stored position after an ordinary stop, not just after an abrupt power loss. If the service provides a watched-history panel, use it to inspect the affected item without deleting the entire account history or changing unrelated viewing settings.
Compare title identity
Different editions can have different durations. Compare runtime, episode number and edition label before assuming two entries represent the same media timeline. An extended edition, recap or differently packaged episode can place the same scene at another time. A title thumbnail alone is not a reliable identity check. If resume consistently jumps to a plausible but wrong point after a catalogue replacement, report the specific entry and duration so support can inspect how history is associated with the asset.
Use a narrow reset
Clear the affected resume entry where supported, rather than every preference. Use a supported restart-from-beginning or remove-progress action for the affected title, then play briefly and stop normally to test whether a new position is saved. Check a second device only after allowing the app's normal synchronization process. Reinstalling may leave remote history untouched while removing local settings. If the bad position returns, record which device or profile reintroduces it rather than repeatedly deleting favourites or credentials that are unrelated to progress storage.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
A new edition of a film is associated with an old saved position from another cut. The stored position belongs to a longer edition whose opening includes extra scenes. Selecting the intended cut and restarting its own history entry restores sensible progress, without deleting another household member's favourites or assuming that reinstalling would rewrite the remote record.
Questions about this topic
Does reinstall guarantee synchronization?
No. Server-side history can remain. A fresh installation may retrieve the same remote history when the account signs in again.
Should all favourites be erased?
Not for one resume entry. A single progress problem is best investigated through the affected profile, asset and history entry.
