ummary:
Enhance JavaScript nodes in the Workflow Editor to support “Error” and “Default” routing options to prevent calls from getting stuck in the node when an issue occurs with the script execution.

Details / Description:
Currently, the only way to move a call through a JavaScript node is by explicitly setting a connection using ivr.setConnection("go"); and then mapping the connection ? to the value of "go" (or whichever name is assigned).

If for any reason the script fails to set the connection properly (e.g., a runtime error, variable not found, or unexpected input), the call will remain stuck in the JavaScript node. This results in dead air for the caller and no fallback path, which negatively impacts the caller experience and reliability of the IVR workflow.

Issue:

JavaScript nodes have no fallback or error handling path.

If ivr.setConnection() fails or is not reached, the call has nowhere to go.

This creates workflow dead ends and can increase call abandonment.

Requested Enhancement:

Add “Error” routing to JavaScript nodes — similar to other nodes in RCX — so the call can be redirected to a predefined fail-safe branch if the script encounters an error.

Optionally, add a “Default” routing option to handle scenarios where no explicit connection is set in the script, allowing for smoother recovery from logic gaps or unexpected conditions.

Example Scenario:
If ivr.setConnection("sales") fails due to an undefined variable, the call would follow the Error or Default path instead of remaining stuck in the node.

Benefits:

Prevents dead air and call abandonment caused by JS errors.

Allows for more resilient and fault-tolerant IVR workflows.

Reduces operational impact from coding or runtime errors.

Improves overall customer experience.