From the aftermath of issue 762005: A problem that made the bug harder to identify and diagnose in the first place, was that many system health stories and the entirety of memory.top_10_mobile "succeeded" despite Chrome haven't being able to load any content at all.

From the debug investigation (comment #112 on that bug), Telemetry could have been able to detect the failed navigation at the following point:

(DEBUG) 2017-10-19 02:26:40,700 inspector_websocket._SendRequest:103  sent [{
  "id": 9, 
  "method": "Page.navigate", 
  "params": {
    "url": "https://www.instagram.com/badgalriri/"
  }
}]
(DEBUG) 2017-10-19 02:26:40,762 inspector_websocket._Receive:170  got [{
  "method": "Page.frameStartedLoading", 
  "params": {
    "frameId": "(CC5854C4E4D92ACC4235D55657C6ADD2)"
  }
}]
(DEBUG) 2017-10-19 02:26:40,800 inspector_websocket._Receive:170  got [{
  "method": "Page.lifecycleEvent", 
  "params": {
    "frameId": "(CC5854C4E4D92ACC4235D55657C6ADD2)", 
    "name": "commit", 
    "timestamp": 4677.87188
  }
}]
(DEBUG) 2017-10-19 02:26:40,800 inspector_websocket._Receive:170  got [{
  "method": "Page.frameNavigated", 
  "params": {
    "frame": {
      "id": "(CC5854C4E4D92ACC4235D55657C6ADD2)", 
      "loaderId": "5829.1", 
      "mimeType": "text/html", 
      "securityOrigin": "://", 
      "unreachableUrl": "https://www.instagram.com/badgalriri/", 
      "url": "chrome-error://chromewebdata/"            ##### <--- NOTE THIS!
    }
  }
}]

And raise an exception here instead of continuing blindly.