Teamcity Gerrit VCS triggering old builds

Hi,

See some topics related to this but all several years old and no real solutions offered. Our builds mostly work as intended with individual commits by users triggering builds on their respective branches. Our problem is that when someone edits either the VCS root or the trigger branch spec (usually involving the gerrit /refs/changes/ branches) TC likes to retrigger all gerrit builds seemingly since the beginning of time. Not only will it rebuild all old builds but triggers multiple versions of each build.

Typically when this happens deleting the builds (sometimes thousands) is all it takes to have things return to normal as new check-ins will work as intended. I assume this is just how it process the previous changes and they're seen as net-new if the VCS modification changes the record in some way. Can someone explain this or what the correct setup is to prevent it when making changes?

Example from today someone modifies branch spec:

before:

1. <param name="branchFilter"><![CDATA[+:/refs/changes/*
2. -:<default>]]></param>

after

1. <param name="branchFilter"><![CDATA[+:*
2. -:<default>]]></param>

TC VCS logs showing triggered builds (also might want to fix reason: per-checking typo, should probably be per-check-in)