Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2023.2.X port as this issue will be resolved in a newer release. The backport to 2023.2 turned out to be more complex due to functionality mismatch. Since 2023.2 is reaching the end of it's support time soon, we recommend upgrading to 6000.X for the fix.