That is probably because the hub didn't have a chance to update the Diagnostic Tool before the database locked up. It could happen in very rare situations. You could follow the steps in this post: