the good news is we have already made the fix to prevent users from making this mistake in the future and it will be released in the next update. Here's a good vote for helping identify the issue. haha