SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Fixing Twilio Event Streams Inbound Message Event Delivery Failures

Issue

Inbound SMS messages sent to Twilio phone numbers are not triggering com.twilio.messaging.inbound-message.received (Inbound Message) event on the configured Event Streams webhook sinks. While outbound message status events (sent, delivered) and A2P registration notifications are being delivered as expected, the Inbound Message event is not reaching the configured webhook destination.

The inbound messages are visible in the Twilio Console, and the standard HTTP webhooks are executing successfully. However, the corresponding inbound message events are not being delivered through Event Streams.


 

Product

Programmable Messaging


 

Environment

Twilio Console


 

Cause

The Enable Message Privacy Features flag (associated with Message Body Redaction in Messaging Settings) is enabled on the Twilio account. Because the com.twilio.messaging.inbound-message.received event includes the raw message body and payload details, enabling Message Privacy Features automatically blocks Twilio from forwarding inbound message events to Event Streams sinks.


 

Resolution

To resolve missing inbound SMS events on Event Streams, update your messaging privacy settings or use standard HTTP webhooks based on your privacy requirements:

  1. Navigate to the Twilio Console.
  2. Go to Messaging > Settings > General.
  3. Locate the Message Body Redaction setting.
  4. Disable the Enable Message Privacy Features flag (this is only available if you have enabled Message Body Redaction) to allow message body content to pass through to Event Streams sinks.  
  5. Save your changes and send a test inbound SMS to verify that com.twilio.messaging.inbound-message.received events are now delivered to your sink destination.

Verification: Send an inbound SMS from an external phone number or another Twilio number and inspect your Event Streams sink destination logs for the com.twilio.messaging.inbound-message.received event payload.

Note: If your organization requires Message Privacy Features to remain enabled due to legal, compliance, or security policies, keep using standard HTTP webhooks ("A Message Comes In") configured on your Twilio Phone Number or Messaging Service. Standard HTTP webhooks capture all inbound message traffic regardless of privacy feature flags.


 

Additional Information

For detailed schema information and event definitions, refer to the Twilio Event Streams Inbound Message Event Documentation.

Have more questions? Submit a request
Powered by Zendesk