Hello,

Following up our previous message please know that the fix for the reported behavior was included in Axigen 10.2.1.12 that is available...