OK, the bug was confirmed in our test center. We will resolve it ASAP.