#30175

We have, btw, updated our license and tried with v3.10.7 as well, but the same problem occurs.