We've identified the issue and are working on a fix. We'll provide another update as soon as we have more information.
