We know that bug is extremely pesky, and the team is very aware of it. We recently asked the community for more information on it and received some great info. While it is not fixed yet, the team knows this item is high priority and is working to get it resolved: