An Azure service for ingesting, preparing, and transforming data at scale.
I do not fully understand you situation, but it sounds like you need more options for controlling flow and logic. I have many tricks that may or may not be helpful. I will share one below.
If I had a diagram of the logic you want to implement, I might be able to suggest a more manageable setup.
I use the below pattern when I I want to branch my control flow, without using an If Activity.
I intentionally cause the set variable activity to fail using an expression like @if(equals(pipeline().parameters.DoSucces,true),true,'IMakeError')
Then I use the dependency conditions to branch my flow. The highlighted 'skipped' dependency is important. Without the highlighted skipped dependency, the pipeline will report failure status.