Hello @Awiener ,
thanks again for reporting the issue and providing the example. We have fixed it with the 1.3.1 bug fix release which we published today. For further details see this post.
Bye
Tobias
1 Like