A catalogue view and its search index can become inconsistent. An item may be visible in a category yet absent from search, or a search result may still point to a record that has changed. Diagnose that mismatch separately from whether the programme itself is playable.
Begin with one known item and a specific query. “Search is broken” is difficult to investigate; “this exact visible title is not returned in this selected scope” is a reproducible observation. Preserve that comparison before refreshing several layers at once.
Check scope before freshness
Some player searches cover only the active source, category or content type. A film visible elsewhere in the application may be outside the current query. Profiles and filters can narrow results further. Confirm those boundaries before treating the index as stale.
Also compare the field being searched. A word present only in a description may not be indexed by a title-only search. A translated label can differ from the stored original. Those are matching and scope questions rather than necessarily an outdated database.
Compare the record and the result
If a search result opens the wrong item, record the result identity and destination separately. Repeatedly renaming the visible title can obscure a broken association without correcting it. The relationship between result and record needs investigation.
- Open the intended catalogue entry through ordinary navigation.
- Record its current title and supported identity context.
- Clear unintended filters and select the relevant source or content type.
- Run a distinctive query using a field the application documents as searchable.
- Use the supported refresh or index-rebuild route if the current record and search remain inconsistent.
Verify the correction specifically
After refresh, rerun the same query and inspect the selected result. A larger result count is not proof that the intended item is now represented correctly. The useful outcome is agreement between current catalogue data, the query and the opened record.
Keep a backup before operations documented to rebuild or replace local data. A narrow search refresh is different from deleting the application’s complete settings. Understand the scope and avoid sacrificing favourites or account configuration for an unexamined search issue.
For support, include the exact query, selected scope, current visible record and observed result. A harmless title example is enough; the full private source export is usually unnecessary. This evidence distinguishes search limitations, stale indexing and incorrect result relationships without claiming that a missing search hit proves service unavailability.
Useful answers
Does no search result prove the programme is absent?
No. Scope, matching rules or index freshness can affect the result.
Can description text be outside a title-only search?
Yes. Check which fields the application searches.
What should be checked after an index refresh?
Repeat the same query and confirm that the result opens the intended current record.