Thanks for the snapshot – we were able to reproduce the issue and will have a fix posted within the next couple hours.