We are aware of this unexpected behavior, and are currently working with our development team to get this resolved. We do apologize for any inconvenience this is causing you.
View solution in original post
