Hey, this was a bug. We recently released a fix for it and shouldn't happen again. Thanks for reporting!

I've passed this on to the development team; I have a good idea why this is happening to this particular model! Thanks for the report!