Error Handling
Steps such as Global Context, Data connections and Language Understanding rely on external services, which can fail when calling them for numerous reasons. In such cases we would like to handle the fail case logic in a flow that is separate from the successful path.
For this reason, steps that may fail, expose a "fail" output node. This node allows to branch from this step to a step that handles the fail case logic. If there's no "fail case" connected, the flow of the scenario continues to the success node even in the case the step has failed. If you haven't connected your scenario to the "fail case" node, it's recommended to check for a successful or failed outcome of the step to apply the correct logic to handle the failure.
