We have a "workflow orchestration" system at work.
It works something like this:
You configure what to run (in a database table), such as:
NameOfStepATHingToRun ="weather_data" RunStepB? = No RunStepC? = Yes StepCArguments = Canada,USA ...
(this goes on with maybe 20 total columns)
Then your configuration is run through a few large functions, with lots of if/else statements
The problem for me is that if I want to change something, like adding a step or having a different way to run a step, then that change affects every workflow - and there ain't a lot of testing going on
It certainly feels like an anti-pattern/design smell to me, but I can't find a name for it