The easy default here would be to have a runbook that executed on a particular inventory group.
The “linear” execution strategy is the default (which you linked to). By default, if there is an error on one host it will continue executing on all other hosts. You need to set a flag to stop executing on all hosts[1].
The parent process would not be notified of any failures until the end of the run, unless you supplied a custom callback plugin[2].
The problem was a human forgot to run a step and no one noticed: The playbook would have failed and the server wouldn't have been online to make orders.
If you read the article, the other servers were fine and did not contribute to the issue.
If you read the article, the other servers were fine and did not contribute to the issue.