We have a build configuration that represents a deploy to a development staging environment. It has a dependency on four other build configurations. It's also set up with a VCS trigger that triggers on changes in snapshot dependencies.
This was working great for some time now. We're currently running TeamCity version 9.1.5 build 37377.
Today we noticed that when this build configuration is triggered by a dependent VCS change, the dependencies build correctly, but the build configuration itself gets flagged as a "history build" (while running there's a warning icon that says "This build is outdated...", and in the history the build is grayed out and says "history" under the "changes" column).
As a result, on the project overview page, the build configuration keeps showing that there are pending changes for it.
Curiously, manually triggering the build configuration correctly treats it as a non-history build, flushing the pending changes.
I took a look at the teamcity-server.log and the teamcity-vcs.log, but nothing stood out at me.
Any advice on how to go about troubleshooting this?