Playback progress describes a viewing state, such as a resume position or watched marker. It is not a new edition of the programme. A catalogue can preserve the work while the application changes or loses the local state attached to it.

Start by identifying where that state is stored. It may belong to a local profile, a server account or an application-specific database. Do not assume a playlist export contains it merely because the exported entries are the same programmes.

A screenshot is not a compatibility test. — IPTV USA editorial illustration

Compare identity and state

If a source refresh creates a replacement record, the new identity may not carry the old progress association. The programme can appear unwatched even though the household watched the earlier record. That is a relationship to investigate, not proof that the content has changed.

Similarly, switching profiles can reveal a different resume point while the catalogue stays identical. Keep the active profile, service account and programme identity separate. A local player profile need not be another service subscription.

Investigate a missing resume point

Do not infer a different cut solely because the resume time looks unusual. Version identity needs its own metadata. Conversely, resuming another edition at the same numerical position may not correspond to the same scene, so preserve meaningful version distinctions.

  1. Confirm the active application profile and intended source.
  2. Identify the exact film version or episode.
  3. Check whether the record was replaced, merged or rematched recently.
  4. Review the documented progress storage and backup behaviour.
  5. Use a supported restoration or correction route rather than duplicating the programme entry.

Keep shared viewing understandable

A watched marker can reflect another household member if profiles share state. Decide which arrangement the application actually supports and what the household intends. Avoid treating a shared resume point as evidence of unauthorized access without checking the configured profile behaviour.

Before reinstalling or clearing data, establish whether progress is included in a supported backup or synchronized account. A restored channel list does not necessarily restore viewing history. Record that limitation while the original setup remains accessible.

For support, name the application profile, exact programme identity, expected state and observed state. Do not include account passwords or an entire watch history when one item demonstrates the issue. The useful outcome is correct state attached to the intended record, with no claim that an export or source refresh universally preserves it across players.

Useful answers

Does a missing resume point prove the programme is another edition?

No. Viewing state and programme identity are separate.

Will a playlist export always preserve watched status?

No. Check the application’s backup scope.

Can switching local profiles change progress without changing the catalogue?

Yes. Profiles can maintain different viewing state.

Keep exploring

Understanding episode numbers in guide dataA poster is a discovery image, not an access recordAn add-on listing is different from a standalone appBrowse every articleQuestions and answers