Hi All.
The organisation I'm working for have set up a basic flow template structure which essentially compresses of a top-level try / catch scope. The 'try' would contain all the main actions of the flow, with the 'catch' handling failure & timeouts, and translates the cause of the failure and notifies an administrator via email. This was primarily done because we had a number of flows that were faulting and we weren't aware of them.
However, I'm working on a number of new flows, while trying to adopt this established template structure, where some actions will legitimately fail, and decisions need to be executed based on these legitimate failures. The problem that I am having is that these legitimate fails are triggering the 'catch' error handling.
In essence, what I really want to do is have nested try/catches as you would in other, traditional programming languages / environments. I've tried this approach and it makes no difference - any failure eventually percolates down to the top-level 'catch' scope.
Does anyone have any design suggestions (other than split everything) or is it possible to cancel a failure some how so it doesn't cascade down?
Many thanks in advance
Mike