@JacksonK.52224 (Customer)​ 

>But this requires me to put my entire worfklow in "try" and then set up an "if error" slack/ email alert.

Correct. The "If/Error" card is a Try/Catch block (in many programming languages) that basically states "Try to do this thing" and if the thing results in an error "Do this thing instead".

Typically the only portions that need to be in the "If/Error" card are actions that are likely to throw an error such as making an API call.

If you want robust handling of specific or a broad set of conditions you will need to build out logic to handle it. If/Error is required if you want to do something after an error occurs in the flow.

@JacksonK.52224 (Customer)​ I used that exact article you mentioned and create one specifically for Successes and Failures > created a completely new private channel for this.

It's becomes like an audit channel that you can use to search to see the history - if you include loads of info, like the email, name if you're using it for custom LCM. You can put the Flow History error URL in a Failure card.

Use https://app.slack.com/block-kit-builder - to make your Slack messages stand out and customised.

I put a Success Message at the end of a WF > pass to child flow to post the Slack message. If it gets to the end of the WF, then everything before it must have worked.

Use the If/Error and create your failure message in the Error part > pass to your "Post Failure" Slack child flow.