Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Twilio Debugger Integration - End User Guide

Pilot Feature

The Debugger Integration is currently offered as a Pilot Feature and has some important limitations.

With pilot releases, our focus is to verify functionality and gather feedback from a limited set of customers. Pilot Features are not covered by a Twilio SLA or support plan.

This is a guide on how to use the Debugger to troubleshoot uncaught exceptions and errors in Flex UI and Plugins. Found in your Twilio console, the Debugger contains a detailed log of activity within your application. This log can help you dive deeper and understand which Twilio resources were impacted (and by whom).

With the integration, you are able to access the following in the Debugger:

  • Uncaught exceptions from the Flex UI
  • console.error messages

Enabling Debugger Integration

You can enable the Debugger Integration on the pre-release features page within Flex Admin.

Pilot Debugger.png

Writing Logs to the Debugger

With the Debugger Integration enabled, any uncaught JavaScript exceptions will automatically be logged. These will include details on the exception, the user who was logged in, and the version of the Flex UI that is being used.

You can trigger custom debugger notifications through console.error statements included in your code.

console.error('Unable to connect to MyCRM: %s', myCRMUrl);

We do not currently support additional levels of logging, like debug, log, info, and warn.

Accessing Debugger Logs

To get to the Debugger, open the console and click on the debugger icon on the top right.

Debugger3.png

Once in the Debugger, you can dig into the details of the logs.

Screen Shot 2019-11-26 at 4.49.43 PM.png

Clicking on a debug event will give you a more detailed view of the event

exception.png

In addition to the user information contained within the notification, the Resource Sid represents the TaskRouter Worker for that user.

What's next?

Now that you've integrated Flex with the Debugger, learn more about customizing the settings in the Debugger and other ways to debug your Flex Applications.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.