Finish Build Trigger not ensuring latest changelist

I used to have "TeamCity Enterprise 2023.05 (build 129203)" but today, I went on and have upgraded to "TeamCity Enterprise 2023.11 (build 147331)"
After the upgrade, I noticed a change and I was wondering if this was a bug.
I have build configuration (conf hereandafter) A, B, C, D 
On build conf D, I have finish build trigger to A, B, C so that after build conf A, B, C finishes, it would trigger build conf D. 
Before the upgrade, what would happen is that build conf D would start from the point build conf A finishes, then when build conf B, C (either simulataneously or not) finishes, it would put one build on the queue. (sometimes two, but this doesn't matter) 
Build conf A would make submit to perforce and so does other build conf B, C, and D. 
So.... each time when build conf D is started it used to start with the latest perforce changelist (revision) 
but after the upgrade to 2023.11 it seems like build conf D would start with the perforce changelist(revision) at the time when it was put on the queue. 
Is there any way to make sure this build conf D always start with lastest changelist?

add) pardon my english.. it's been awhile since i've used it.. sorry.