The issue of limited internet connectivity is tricky, but I'm wondering if we can try to catch the exception that is thrown and suggest limited internet connectivity may be causing an issue, checking their internet connection and either closing the analysis view or restarting Ergo/NIST-CORE might help. There was an issue that came up in the training where it looked like a default dataset might be broken because not all of it was retrieved from the remote site and the analysis would not complete correctly; however, restarting Ergo/NIST-CORE seemed to force it to refetch and the analysis succeeded. I'm attaching the log, the relevant section seems to be the load local dataset task. Maybe we can catch the null pointer and display a message to the user.