Hello @weedor,
Thanks for the report. This should be fixed with 1.2.2.3.2.
If you still experience this issue, please let us know by replying to this thread.
Thanks!