Hey @Zambookii

We’re aware of this issue and it’s been fixed internally. It’ll come out as a fix in an upcoming patch.
Thanks for your feedback.