A player can refresh source data when it starts, depending on its settings and implementation. Reopening may therefore reveal additions, removals or corrected labels that were not visible in the previous session. That is different from the application software updating itself.
When the list changes, identify whether the source, active profile or local view changed. A familiar home screen does not prove that the same data snapshot is loaded. Keep the actual startup behaviour tied to the documented application.
Compare the source and the view
A remote maintained catalogue can legitimately change between sessions. A local snapshot may remain unchanged unless another process replaces it. The player’s startup routine determines when it reads or rebuilds that data; the source determines what is available to read.
A sort or filter preference can also make the list look different without changing the source. Confirm the active view before reporting missing entries. A profile switch can select another arrangement altogether.
Investigate a startup change
Do not disable updates permanently merely to preserve an unexplained appearance. That can leave retired sources or old guide mappings in use. If a source correction disrupts personal organization, recover the local preference separately from the current operational data.
- Record the source label and view used before closing the application.
- Check the documented startup refresh settings.
- Reopen and identify the actual active source and profile.
- Compare a specific known entry or correction, not only the total count.
- Record whether the change came from refreshed data or another local selection.
Preserve personal state intentionally
Favourites and local labels may survive refreshes differently across applications. Check where they are stored and whether they attach to stable entry identities. A replacement record can look new to the player even when it represents a familiar programme.
If startup repeatedly returns an error, preserve the exact message and note whether an older cached list remains visible. A visible list does not prove the latest retrieval succeeded. Conversely, an empty view can reflect a failed refresh rather than a deleted account.
For support, describe the startup setting, active source and exact before-and-after difference. Keep private addresses out of screenshots. The useful outcome is predictable refresh behaviour with current source data and understandable local preferences, rather than assuming that every changed list means the app reinstalled or the account was reset.
Useful answers
Is startup source refresh the same as a software update?
No. It concerns data retrieval or rebuilding.
Does a visible cached list prove the latest refresh succeeded?
No. Check the actual retrieval result.
Should current source corrections be discarded just to preserve old ordering?
No. Restore personal organization separately where supported.