Hi gents,

we are also dealing with this issue in our company. It was first detected by XRAY this year in May if I remember correctly. We have deployed the newest version 1.2.6 this month, but the issue still occurs. Are there any estimations, when the fix will be available?

Many thanks in advance for your support!

Best regards,

Sascha