Hi @alessykora,
we are aware of this bug 
and we already have a working solution in our dev version, so it should be available in the next update.
Because this issue was already reported, I’ll close this topic and mark it as a duplicate. Here is the original report, which we will also update once the fix is released:
Thank you,
M