#29048

@PD4ML wrote:

We spent quite a lot of time on the issue, but were not able to reproduce it. Probably the current development state implicitly solves the problem.

We are going to release new beta on Monday. Please give a try to it and let us know if it changes anything.

OK I look forward to trying the new jar.