Hello @UlrikSeip, we are aware of this bug and currently working on it.