91300: Event delivery to destination failed

Twilio records this generic delivery failure error when Data Destinations cannot deliver an event to your configured destination and the failure does not match a more specific error condition.

This error serves as a generic fallback and is recorded when Twilio cannot identify the precise root cause such as a timeout, connection error, or specific HTTP status.

• A non-webhook destination (such as AWS Kinesis, Segment, etc) rejected the write payload due to invalid stream names, missing permissions, or invalid credentials.
• The destination rejected or dropped the delivery payload under conditions that fall outside standard HTTP or protocol-specific error categorizations.

• Review your destination error logs for more granular errors that provide specific remediation steps.
• Verify that the destination actually exists, is active, and is not in a deleting or paused state.
• Ensure that the API keys, IAM roles, write permissions, or authorization tokens configured on the destination are active and have write access to the destination.

• 91305: Destination endpoint rejected the event
• 91306: Destination endpoint returned a server error
• 91307: Could not connect to destination endpoint
• 91308: Destination endpoint did not respond in time

• Data Destinations overview
• Create a destination
• Create a subscription