My first thought is that the blocks downstream from the ansible block don't require it to complete, while the blocks downstream from the splunk block do. To check on this: Click on all downstream blocks For each, open the advanced dropdown in the left panel See if the Join Settings require the ansible/splunk blocks If you don't want the block to be required, uncheck the box here To directly answer your title question, you can build your own error handling by placing a decision block after the splunk block to check whether splunk_block:action_results:status returns success or failed. If you take this approach and have the different branches reconnect at any point, you'll have to check the join settings because they will automatically require the splunk block to have completed even if your playbook previously followed the "failed" path.
... View more
