This behavior is the same with the current rev. 102.1.
I believe this to be a bug.
You should open a support incident for this.
This behavior is the same with the current rev. 102.1.
I believe this to be a bug.
You should open a support incident for this.