We have updated to 2.1.0p1 and can confirm that the issue is now fixed.
Thanks to the Team for a quick response to this!
1 Like
We have updated to 2.1.0p1 and can confirm that the issue is now fixed.
Thanks to the Team for a quick response to this!