A hotfix has been deployed for this issue and it should now be resolved. Thank you for your patience.