Thanks for the heads up @gf_wolfer.
As an FYI to the Bubble team, the one challenge this would create for our application (if we created it from scratch today) is that by separating this 1 action into 2 actions each with different trigger conditions is that we often have to reference this step in future actions in the same workflow. Currently, there isn’t a way to reference “step 1” if step 1 passed and if not then “step 2”. As such, we’d have to duplicate many of the workflows that follow (one action that references step 1 and another action that references step 2, each with the corresponding trigger conditions).
So, I’m glad it’s not deprecated on our app. Seems entirely solvable though with an upgraded way to reference other actions. Probably not a high priority at all though, imo.