Stop a maintenance/onboarding session if critical task/software fails to verify

We have maintenance tasks and onboarding tasks that are prerequisite for later tasks to deploy correctly.
Having a feature like the “prerequisite” for software, or perhaps an overarching “validate” feature, could enable us to prevent manual intervention when a deployment task fails.

So I’ve encountered this before.

Why would you want to completely stop a process over one item, when it can be addressed after the fact?

How would stopping the session eliminate manual intervention?

The scenario in question is that the “Create primary user profile” is a prerequisites for some of the other tasks targeting default user profile.
We would then have to correct the issue, and re-run the onboarding.

However, as you say - this does require manual handling as well.