Hi @GSpot,
The recent update didn’t include a fix for this new issue - sorry if there was any confusion there!
Since our team was able to reproduce the issue internally and we already have a ticket open with our development team to address it, there aren’t any next steps needed from you at this time. Because of that, we’ll go ahead and close this thread. You can expect a fix to be included in the next update or so - and of course, will be included in our software release notes that you can access here:
Thanks again @GSpot! 