Hi @qiang814k, @nadim, @Jonas, @jornes and @mat5ch,
This issue should now be fixed with 1.3.2. Kindly let me know if this is the case on your ends.
Thank you.