We've fixed the issue. If anyone else encounters it, please let us know. Thank you for your feedback and support.