Documentation for TC 9.x describes quiet period as follows:
A quiet period is a period (in seconds) that TeamCity maintains between the moment the last VCS change is detected and a build is added into the queue. If new VCS change is detected in the Build Configuration within the period, the period starts over from the new change detection time. The build is added into the queue only if there were no new VCS changes detected within the quiet period.
If I have a VCS trigger rule that is an exclusion (e.g. -:%SOME_PARAMETER%/Foo/bar.txt), if a change is made to a file that matches that rule during the quiet period, will the quiet period restart? It seems like it shouldn't, but I'd like to know what is the expected behavior by design.