I tested this with the latest product 2.3.2 and the problem still occurs. Please open up a support incident with Customer Care for this and we will submit it to Development as a bug. Thanks.
↧