Thanks for getting back to us.
We have tested the scenario in our environment and managed to replicate the issue. Hence, for the sake of correction, we have logged it as PDFNET-43917 in our bug tracking system. We will further investigate the issue and keep you posted with the status of its resolution. Please be patient and spare us little time.
We are sorry for the inconvenience.