Twilio offers several tools for investigating the interaction between Twilio and your application. If a message fails to go through, is delayed, or otherwise behaves unexpectedly, these tools should be your first stops for debugging.



How to navigate to the Messaging Logs and how to use them?


You can view the error logs for your Twilio account by going to the Twilio Console. You can use this log to get an idea of which Twilio resources may be affected and who was responsible for them.



Log on to Twilio https://console.twilio.com/



Go to the top right -> Click Account -> Click Subaccounts




If there are too many subaccounts inside Twilio, you can go back to HL and copy the Account SIN for that location to search in Twilio:





Now go back to Twilio with the copied Account SID

Search based on the Twilio Subaccount SID in agency level settings -> Twilio
Paste the Account SID here and click on it:





Once you are in the subaccount inside Twilio


Head to the Left panel, Click Monitor > Logs > Messaging





Put the contact's phone number (remove all phone format) in the FROM / TO field:


FROM field: Contact's incoming SMS


TO field: Outgoing SMS







From there, look for the message where the problem happened. Click the hyperlinked dates to go deeper into the details for each message. You’ll notice messages that don't hit a  200   are highlighted in either yellow or red.



As you can see above, each log line includes the number of message segments, the message status, TO and FROM numbers, as well as if any media was attached.

If it says delivered but the contact is not receiving it, grab this Message SID and open a ticket with Twilio support at support@twilio.com






In the detailed view of the message log, you can find the Message SID (Twilio's unique identifier for this message), as well as the time the resource was created, TO and FROM numbers, Delivery Steps, and the Request Inspector.



The Delivery Steps section of this log will show you when the request was created, how long it was queued on Twilio's platform, and when it was sent out to our carrier partner for delivery. These factors can help you determine where an undelivered message failed, or investigate latency issues.



The request inspector shows all requests and responses made when sending or receiving this message. You can easily see errors on requests by the color-coded status on the right of a request.




In the above response, we can see that we received a 404 response because Twilio was unable to find the tunnel for the webhook we set up for messages.




If you hover over the records, it will preview the content of the message.