Hi @nvivot,
Thanks for reporting this in this thread as well. As Tommy mentioned here, our team is working to address this and it will be fixed in the next release.
Best, Will