Mateusz Blaszczyk wrote: > It seems it's a bug that appeared first in 12.2(50)SE and later releases. > To be fixed in SE3, scheduled for release on 23th July. Thanks for the info! -- Tim