Hi @Patrick, thank you for reporting this bug. We are already aware of this issue, and It’s been discussed here:
I’m closing this topic as a duplicate.