The issue has been identified and a fix is being implemented.
We are currently investigating this issue.