We're working on implementing a fix for this issue, and it should be completely rolled out over the next 3-4 hours.

Thanks for your patience.