error.badfetch

This event is thrown when a resource fetch has failed and the interpreter context has reached a state where the resource is required. Fetch failures result from missing resources, unsupported scheme references, malformed URLs, client aborts, communications errors, timeouts, security violations, unsupported resource types, resource type mismatches, document parse errors, malformed documents, and a variety of errors represented by scheme-specific error codes. See error.badfetch.{protocol}.{response code} for details.

If the Voice Browser service has prefetched a resource, either by explicit VoiceXML directives or speculative optimization (fetching a resource the user is suspected to access), and that resource turns out not to be needed, the error.badfetch event is not thrown. Likewise, the error.badfetch event is not thrown if the fetch of an audio document fails and if there is a nested alternate whose fetch then succeeds.

The Voice Browser service throws an error.badfetch event within the document that requires the corrupt resource. For example, if document A requires document B, and document B is corrupt in some fundamental way (element arrangement incompatible with VoiceXML syntax, document does not exist on server, or document does not load in time), the error.badfetch event will be generated in document A at the time document B is required. The error.badfetch event is not generated in document B. 

Note: ECMAScript initialization errors such as voicexml-level scripts and invalid variable assignments occurring in document B will not cause an error.badfetch event in document A. Instead, these types of errors will result in error.semantic events in document B.