"Sonar Way" quality gate now considering non-new code

We have a legacy project that we’ve added Sonar Cloud to, and are using it to track our new code.
Unfortunately, it seems as though it’s triggering on old code - specifically, HTML and XML (though not Java, or JSPs) even though the quality gate is supposed to not consider old code.

Is this a bug in Sonar Cloud? Is it being addressed?

This is not supposed to work like this, indeed. However, without an example to look at, it’s going to be difficult to troubleshoot. I guess your project is not open-source?

No, it is not open source. Additional piece of information that may help: we have changed nothing in our sonar configuration; this just suddenly started happening.
Perhaps I’m going about this the wrong way.

Is there a different support mechanism for bugs in sonar cloud for paid members?

The support channel is the same. However if this can help us investigate this potential bug, please send a message on the contact form providing a reference to this thread, and giving more details about your organization, your project and whatever can help troubleshoot this. Thanks!