Hi @alexximalaya! This bug has been fixed in QIIME 2 2017.12, which was released yesterday! If you regenerate this visualization with the latest version you shouldn't encounter this bug anymore. Thanks! 
Hi @alexximalaya! This bug has been fixed in QIIME 2 2017.12, which was released yesterday! If you regenerate this visualization with the latest version you shouldn't encounter this bug anymore. Thanks!