In TeamCity, I have two build configurations: Build A and Build B. Build B has a snapshot dependency on Build A and is set to trigger via a finish build trigger when Build A completes.

When I trigger 5 builds numbers in build A I expected for each when its finished to trigger build B.

Here’s the scenario:

1. I triggered 4 builds for Build A. These builds are scheduled to run on Agent X. At any given time, one build is running, and the remaining three are queued.
2. Build B is also configured to run on Agent X.
3. When the first instance of Build A finishes, it correctly triggers Build B. Build B is then queued because the next instance of Build A starts running immediately.
4. The issue arises here: when the second instance of Build A finishes, I expect it to trigger another instance of Build B, resulting in two builds queued for Build B. However, I only see one queued build for Build B, not two.
5. This pattern continues, and in the end, only one instance of Build B runs, despite triggering four instances of Build A. I expected all four instances of Build A to pass through Build B.

The VCS root is connected only to check out the latest code from a branch.

I do see that Build B is triggered after Build A finishes, but not consistently for each instance as expected.