We are aware of this issue and are currently working to implement a hotfix to address this. More soon