Node Log File Browser timeoutIssue - When using Node Log File Browser the session gets timeout without giving any results.- Issue happening only in production and not happening in non prod instances.Cause The reason why the Node Log File Browser keeps timing out because the localhost logs are too large and takes a very long time trying to parse through all the logsResolution Here are a couple of solutions that can work for you: Solution 1 (RECOMMENDED): You can also Navigate -> System Logs > "Node Log File tailer " to tail the current logs of the node you are currently logged into. Solution 2 (RECOMMENDED): You can review the below KB to download localhost logs. Documentation: https://support.servicenow.com/kb_view.do?sys_kb_id=075d15a6db12ef406c1c02d5ca961921 NOTE: When the localhostlog downloads, you can use the below commands to find any string in the localhostlog that will be very much faster than using the Node Log File Browser module. - If you using Windows, below is the command you can use in the DOS command line to search for any string on any file: FINDSTR COMMAND - https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/findstr- If your using a Mac or Linux Terminal, then you can use the below command to search for any string on any file: GREP COMMAND - https://linuxhint.com/grep_command_linux/ Solution 3: You can try using the Node Log File Browser module at 00:00 PST since thats the time a new log file starts generating a which means that it will not need to parse through too many log lines to provide you results. Solution 4: You can try to disable the debug related properties so that it logs less lines and see if the Node Log File Browser module works from the day after disabling the properties and so on.