I found a workaround that will solve your problem
Excluding Oracle support tickets, because I don't want to remember any more about those than I already do, my most interesting experience was with a certain unnamed software supplier. We had an issue making use of one of their components, and my junior opened a support case. A few fruitless weeks later, he and I had come up with a workaround that was time-consuming and painful to implement, but did at least get the thing working. We reported this in the support case and closed it off (I don't remember if that was at our instigation or theirs, but there didn't seem to be any prospect of actual help).
A few years later and on a later version of the software, I encountered the same issue and opened another support case. After about a week, they declared that they had found a solution for us... which was a copy and paste of the workaround we had found the first time.
Incidentally, we found out that the issue was caused by their use of a third party component. Which does have a switch to enable the behaviour that would have resolved our problem.
I had to do the same workaround again just recently, on a much more recent version of the software. I didn't bother opening a support case (it would have been useless anyway as they want everyone to stop using the on-premise version and migrate to their shiny new cloud version, which is at least 75% compatible with all the stuff we've built on it, and only costs about 5-10 times as much).