@premier Turns out this was a bug in the code. This is now fixed in latest dev-branch version. With the new official release on the door step your should update to 1.5.10 as soon as it’s out.
PS: If you’d kept up the topic and offered more information we might have been able to fix this way earlier.