1 of 1 people found this helpful
This is a known issue that affected both Public and our Corporate Server product. A fix is being investigated currently and will be pushed to Public when it is fully addressed.
Sorry for the inconvenience.
Thanks, Dan, appreciate the update.