Hey Rachel. Sorry about the delay in responding; for some reason your comment had been marked as SPAM and I’m just noticing that now. This issue you’d reported is a known bug that has been fixed for the 2.0.2 release, which will be launching either this evening or tomorrow morning. Upon upgrading it should be resolved but please let me know if it’s not.