We’ve found and fixed this bug. The fix was deployed at 12:00 Noon PST today, and will appear in our next hotfixes update.