Unfortunately, your report is not unique. When I first saw the title, I thought, “Here we go again…”
I was sure I had already read other reports here on the forum about this same issue.
It might be worth reaching out to those people to see how the situation was resolved and even sending that information to support as evidence that this bug has occurred before.
