That’s odd. Someone else reported this same issue. I see you are using v4.1.71 … I wonder if this other user was on the same version, and it is specific to v4.1.71… can you upgrade to at least 72 and test again?
That’s odd. Someone else reported this same issue. I see you are using v4.1.71 … I wonder if this other user was on the same version, and it is specific to v4.1.71… can you upgrade to at least 72 and test again?