Twilio is launching a new Console. Some screenshots on this page may show the Legacy Console and therefore may no longer be accurate. We are working to update all screenshots to reflect the new Console experience. Learn more about the new Console.
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
The debugger is enabled by default. You can enable or disable the Debugger Integration on the features page within Flex Admin.
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
To get to the Error logs, open the console, click the Monitor tab and click on the Error logs under the Errors menu.
Once in the Error logs, you can dig into the details.
Clicking on a debug event will give you a more detailed view of the event
In addition to the
user information contained within the notification, the Resource Sid represents the TaskRouter Worker for that user.
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.