We're terribly sorry for this, it's a bug we addressed in this post, and are currently working on fixing in the public version.