Hi @gagathos,
We are aware of this issue, and it will be fixed in one of our upcoming releases.
Thanks