> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/troubleshooting/network-explorer.md). # Network Explorer ## Overview Explains symptoms experienced when viewing the Network Explorer Tree and the associated controls. ## Tree search does not find a watch If the watch definitely exists in Highlight, possible reasons causing no search results are: * Search selection has been set to "Folder and below" rather than "Global" * The watch has "show data" unchecked, which hides the result from a search. If you have Admin permissions, then an Admin search will find an existing watch. Note that an Admin search is limited by what is selected in the tree. ## Folder/Location still grey after watch activated A grey folder or location normally indicates that it contains no activated watches. Following activation of a watch, you may need to click Reload Tree to refresh your view of the Tree. ## Folder/Location not grey despite having no watches visible A yellow folder or green location pin normally indicates that it contains at least one activated watch. * Following deletion of a watch, you may need to click Reload Tree to refresh your Tree view. * The watch has "show data" unchecked, which hides the result from view. If you have Admin permissions, then an Admin search will find an existing watch. Note that an Admin search is limited by what folder or location is selected in the tree. * The watch has a visibility setting higher than your access. For example, a watch can be set with visibility Internal so it is not visible to end customers. ## Tree showing locations out of order Newly added locations appear at the bottom of the list in the Tree. Click Reload Tree to refresh your view of the Tree. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.highlight.net/troubleshooting/network-explorer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.