Objective

This article helps you inspect the per-recipient results inside a message operation, including how many attempts each message took and whether a fallback channel was used, so you can troubleshoot specific delivery failures.

Product

Communication APIs

Environment

Twilio Console

Procedure

1. In the Twilio Console, select Communications in the left sidebar.
2. Open the Communication APIs Operations page.
3. On the Messages tab, select the operation you want to inspect.
4. Scroll to the Communication messages section. Each row shows the message ID, Status, Attempts, Fallback used?, and Body.
5. To see the delivery attempts for one message, select the arrow at the start of its row. The row expands into an Attempt 1, Attempt 2, and so on sub-row, each with its own status.
6. To narrow the list, select Status above the table, choose a status such as Delivered, then select Apply.
7. To find one message, enter its ID in the search box above the table.
8. Select Next below the table to move to the next page of messages.

Additional Information

• Fallback used? shows Yes when the message needed more than one attempt to reach the recipient, and No when the first attempt succeeded.
• Message statuses are Queued, Scheduled, Sent, Delivered, Read, Undelivered, Failed, Canceled, Group, and Inbound.
• The table loads 10 messages per page, and the attempt and content details for those rows are fetched separately. Attempts, Fallback used?, and Body briefly show placeholders while that data loads.
• If the extra details cannot be retrieved for some messages, those columns show - and a notice names the affected message IDs.
• If nothing matches your filters, the table shows No results found — try adjusting your search or filters.

This content was generated by AI and reviewed, edited, and verified by a human.