When an action stops/errors, subsequent actions are now running. Shouldn't the Zap stop running following actions?

I’ve been using Zapier for 2+ years and recently noticed that when an action in a Zap stops or errors, the following actions are still running and consuming tasks.

For example, I have an action that creates a user in app #1, and then an action afterwards adds a spreadsheet row to app #2 (e.g. “user created”). If the action fails to create a user in app #1, the app shouldn’t add anything to the spreadsheet in app #2. However, what is happening, is that the user is not created in app #1, yet the spreadsheet row in app #2 is added regardless.

Did Zapier change this mechanism or am I imagining it? I realise that subsequent actions may not run if the previous action was related (from the same app, or if there is an option to not proceed if the step failed). Until now, I expected and observed that following actions will not run if a previous action does not complete successfully.

In my example above, I would need to add a filter action inbetween the actions to proceed only if the prior action was successful. In a complex Zap, I might need to add multiple filter actions, this will quickly add up on tasks being consumed. If this is also true, I will need to update many existing Zaps I have built for clients. This is very discouraging and would encourage me to use Zapier alternatives.

The logical path would be to stop any subsequent actions from running if a previous action stops or errors. Perhaps I’m mistaken or haven’t considered other angles, but this new logic only benefits Zapier to reap more tasks and revenue. Keen to hear if others have noticed this or if there was an announcement made somewhere, or ideally, if a setting exists so that across my entire Zapier account I can stop Zaps running subsequent actions when an action stops/errors.