Adobe confirmed that it is a bug and they replied the below in the support ticket.After I discussed this issue internally, I came to know that there is already a bug created for the engineering team until the engineering team fix this issue, here is the workaround team shared with me which I tested ...