A player’s search can cover a defined part of the library rather than everything configured in the application. The active source, content type, profile and filter can all affect the result. Establish that scope before concluding a programme is absent.
The query’s target field also matters. A title search may not include descriptions, alternate names or guide events. A familiar topic mentioned in a synopsis can therefore produce no result even when the programme is visible elsewhere.
Define the intended search
Decide whether you are looking for a channel, a scheduled programme, a film, a series or an episode. Those identities can live in different parts of the interface. Searching a channel list for an episode title may ask the wrong index.
A local profile can also restrict the visible library. A result absent in that profile is not automatically absent from the source. Keep the authorized context clear without switching into another person’s account casually.
Check the scope deliberately
If the item is visible in the same documented scope but cannot be found by a supported query, index freshness or matching behaviour becomes a more relevant question. That is a later finding, not the starting assumption.
- Identify the kind of item you want to find.
- Confirm the selected source, content section and active filters.
- Read the application’s documented searchable fields.
- Use a distinctive known title or identifier supported by that search.
- Compare ordinary navigation if the query still returns no expected result.
Keep alternate naming useful
A translated release title can differ from the stored original. Try reliable alternate names where appropriate, but do not treat a similar result as the same work without identity context. Accents and script handling can also depend on the application’s matching rules.
Avoid stuffing extra keywords into visible titles to compensate for a limited search. That can make the catalogue harder to recognize. A supported alternate field, clearer scope or specific developer correction is preferable to distorting programme names.
For support, include the exact query, selected scope, relevant visible entry and expected result. A harmless title example is enough to explain the issue. The desired outcome is predictable discovery within an understood search boundary, with catalogue absence and account availability kept as separate claims.
Useful answers
Does player search necessarily cover every configured source?
No. Check the actual scope.
Can a title search omit description text?
Yes. The indexed fields depend on the application.
When should stale indexing be considered?
After confirming that the current item lies in the documented searchable scope.