Hi @haddi77, Thanks for sharing the details. Our team has fixed this issue. Please wait for the next extension release and then share your findings with us.