Errors

Browser sessions report problems as a VoxioError. The server SDK throws a VoxioServerError. Both carry a code you can switch on.

#Catch browser errors

Listen for error on the session:

1session.on("error", (error) => {
2  // error.code, error.message, and error.status for HTTP failures
3  if (error.code === "mic-denied") showMicHelp();
4});

Widgets fire the same error as a voxio-error DOM event, and React components call onError.

#Browser error codes

#Catch server errors

Wrap server calls and check the code:

1import { VoxioServerError } from "voxioagent/server";
2
3try {
4  await voxio.flows.update(flowKey, { name: "Support" });
5} catch (e) {
6  if (e instanceof VoxioServerError && e.code === "not-found") {
7    // the flow key is wrong or the flow was deleted
8  } else {
9    throw e;
10  }
11}

The error's message is the service's own, with its request id when there is one. Quote the request id if you contact support.

#Server error codes

#Next steps

• Headless sessions: see how reconnects and retries work.
• Server SDK: set timeouts and retries for server calls.