this is something support needs to investigate.
yes we opend some cases for this issue and we tried to find solutions within the documentation. I got one new feedback and we now check if that helps.
We have the same issue on our side but not solution for now.
I'm interesting to see your feedback.