#30167

The issue has been fixed in forthcoming v3.10.8. The feature always works correctly in PD4ML v4 snapshots