We have tested the scenario in our environment and were able to notice the issue. We have logged it as PDFNET-47530 in our issue tracking system. We will further look into details of the issue and keep you posted with the status of its correction. Please be patient and spare us little time.