The “Error handling” section allows you to configure the behavior of scenarios in which unexpected component failure occurs.
In case of unforeseen technical faults during the execution of a component, the call will have the behavior specified in this section.
This section is available in every Studio component. The only exceptions are the initial and terminal steps.
Within the “Error handling” section, you can select any of the following options:
In the “Studio Flow Execution Report”, this error exit will always be presented as an "error", independently of choosing "End flow", “Follow exit”, or a custom exit.
Once "error" shows up in the report, in the case of "End Flow", no new line will be presented. If there are next steps defined following a custom exit option or an existing one, they will be displayed in the report and new lines will be presented.
Each Studio component has a default, prebuilt behavior, responsible for handling the call in a predefined way in case an unexpected error occurs. When the option “Use default behavior” is selected, the error will be handled according to this prebuilt behavior. A caption is displayed under the dropdown to apprise users of the component’s default behavior.
On the right-hand side, the “Reset to default” button is displayed. If the “Use default behavior” option is selected, the button will be greyed out, since the component is already using the default exit in case of unexpected failure.
However, if any of the other options on the dropdown menu are selected, the button will become clickable to always enable you to return to the default behavior without having to select “Use default behavior” from the dropdown.
In the example shown above, the default behavior for the “Assignment and Dial” component is “End flow”, which terminates the flow in case of faulty behavior.
In the table below, you can see the default behavior for each component:
Assignment and dial
Connect virtual agent (Voice)
Estimated waiting time
Forward to external number
Salesforce data dip
Send SMS Notification
Send SMS Notification with Reply
Contact Not Enrolled
Assign Agents to Chat*
Connect virtual agent (Digital)*
Make outbound call*
Given the fact that the Voicemail component is final, does not have an “Exits” tab, and exits cannot be configured by the Flow Administrators, an unexpected failure during the execution will automatically assume the "End flow" behavior".
Components marked with an asterisk (*) are in Early Access and only users under this program are able to use them. For more information about these components, or the Early Access program, please reach out to your Customer Success Manager (CSM).
If the “End Flow” option is selected, the flow will be immediately finished in case an unexpected error occurs.
If the option “Follow exit_name exit” is chosen, in case of malfunction, the component will assume the behavior specified for the selected exit and will follow the same transition.
In the example shown above, by choosing to follow the scenario configured under the “No answer” section, we can see that, if an error occurs, the call will be forwarded to the “No answer message” step, which will play an audio message to the caller.
The number of “Follow exit” options available in the dropdown will always be equivalent to the component’s mandatory and optional exits.
When selecting the “Define custom exit” option, you can add a new step to the flow and direct it to an exit of your choice in the “Send to” field.
In case of a critical component, such as “Assignment and Dial”, we strongly advise Flow Administrators to configure the section with the behavior they want to offer to contact persons, so the flow is able to continue through that path, in case an unexpected error occurs.
Updated about 2 months ago