Kodi / documented application workflow · Publisher-documented application guidance; UK IPTV account compatibility not tested. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Identify the log being discussed
Kodi has several sources of diagnostic information. The Event Log is the user-facing list of activities such as failed library scraping, add-on updates and PVR events. It is not interchangeable with every debug-log file or an operating-system crash report. Name the screen or file before interpreting an empty result, because different logs have different retention and detail.
Keep the session boundary in mind
The official Event Log page describes it as read-only and says it clears when Kodi restarts. An empty list after restarting therefore does not prove that the preceding operation succeeded or that no error occurred. Record a useful entry while it is still available, checking it for private details before sharing. Do not repeatedly restart and then use the cleared screen as evidence of a clean test.
Reproduce the narrow operation
For a missing library title, repeat the relevant library update and inspect the new Event Log entries. For a timer or PVR problem, preserve the event associated with the specific action and its time. Avoid generating a long collection of unrelated activities before capturing the result. A small, clearly described reproduction helps distinguish the action that failed from background activity that merely happened nearby.
Use filters without hiding the relevant context
The documented screen offers level and ordering controls. State if a filter is active when a screenshot appears empty, and retain the exact message rather than just its colour or warning icon. Escalate to the appropriate detailed log only when the support question requires it. This article explains the session log’s behaviour; it does not report a Kodi or UK IPTV account test.