Browser developer tools · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
The visible list has a recording policy
Firefox documents that its Network Monitor clears on navigation or reload unless Persist Logs is enabled. Chrome provides Preserve log for keeping requests across page loads. A request missing from the current table can therefore reflect how the log was retained, rather than proof that the browser never attempted the earlier action.
Consider a sign-in transition
A harmless reproduction might start on an information page and then navigate to another page before the error appears. If the log resets at that transition, the preceding request may no longer be visible. This is an illustrative capture problem, not a conclusion about the sign-in system or a reason to include credentials in a shared file.
Capture the necessary boundary deliberately
If trusted support needs that transition, start from the nearest safe preceding step and enable the relevant preservation control deliberately. Keep the recording bounded and stop afterward. Retaining more requests also increases the information that needs privacy review; it should not become an instruction to record an entire unrelated browsing session.
Describe the limit in the report
Say whether log preservation was enabled and when the capture started. If the earlier step was not retained, mark it missing rather than inventing a successful or failed request. A clear description of what the trace includes is more useful than treating a partial table as a complete history of the task.
Questions, answered
Does a missing row prove a request never occurred?
No. The log may have been cleared or recording may have started later.
Should preservation stay enabled for unrelated browsing?
Keep the capture bounded to the necessary task.