Error Handling

Error Handling

Creating an application or website that works correctly is what every programmer attempts to do, but inevitably either the programmer or the user will make a mistake. Error handling allows an application to continue to work after something incorrect or unexpected has occurred. Successfully handling errors requires a programmer to find and prepare for any issues that may come up within an application or website.

A developer always wants to hide irrelevant details about the error from the user. Outputting long and complicated messages that come back from a server is not a good design practice. These messages may even reveal important or sensitive information concerning the application or website that users are not supposed to see. Better practices would include finding out what type of error occurred and then outputting a friendlier message that you control.

There are many different types of errors that could occur. Being able to predict and implement handlers are an important step toward making a good website or application.

One common IVR error is the “badfetch” error. This occurs when the platform is attempting to find an application at a URL, but was unable fetch the URL or received invalid VoiceXML. To fix this error, you should check that your URL is pointing to valid VoiceXML, and that the server is accepting outside connections. If this error occurs during the course of a call, by default the call will end immediately after the error message, but if you set an error handler in your VoiceXML you may be able to redirect the caller to an operator instead. See the first related link below for more details on this technique.

Related links:

Related terms

for "Error Handling"

Search Glossary

Term of the Day

The maxspeechtimeout property indicates the maximum duration of users speech input.
See also: Property, Tag, VoiceXML