Build chain snapshot dependencies and VCS triggers for incremental builds

Hi Team,

We have following build configurations and their snapshot dependency:
--> : Depends on

B_C --> AA
B_L --> B_C
B_N --> B_L
B_f_cpp --> B_C, B_L, B_N
B_f_c# --> B_C, B_f_cpp
B_p_c# --> B_C, B_f_cpp
B_p_cpp --> B_L, B_N, B_p_c#, B_C
B_U --> B_C, B_f_cpp, B_f_c#, B_L

I had added snapshot dependencies for B_C, B_L ,B_N, B_f_cpp, B_f_c#, B_p_c#, B_p_cpp, B_U configurations.
If a build tree is drawn from the above configurations then lowest leaf configurations are B_U and B_p_cPP.

I had added VCS triggers for B_U and B_p_cPP with Trigger on changes in snapshot dependencies option enabled.

If I do VCS changes(push/commit operation) in B_U configuration then
Build order: B_U.

If I do VCS changes(push/commit operation) in B_p_cpp configuration then
Build Order: B_p_cpp.

If I do VCS changes(push/commit operation) in B_p_c# configuration then
Build order: B_p_c# , B_p_cpp.

Uptill now configurations are working fine but
If I do VCS changes(push/commit operation) in B_f_c# configuration then
Build orders is:
B_C, B_L, B_N, B_f_cpp, B_p_c#, B_p_cpp, B_f_c#, B_U

But in this case build order should be:
B_f_c#, B_U only

Same for
If I do VCS changes(push/commit operation) in B_f_cpp configuration then
Build orders is:
B_C, B_L, B_N, B_f_cpp, B_p_c#, B_p_cpp, B_f_c#, B_U

But in this case build order should be:
B_f_cpp, B_f_c#, B_U only
|
|-----------B_p_c#, B_p_cpp

Any Idea on above issue?

Referred TC post:

https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206237579-Joining-build-dependency-triggers-and-conditional-builds