91308: Destination endpoint did not respond in time

Twilio records this error when Data Destinations establishes a connection and transmits an event to your destination, but the destination fails to return an HTTP response before the timeout limit is reached.

Because Twilio did not get a response from your destination, Twilio will automatically retry event delivery per retry policy. To prevent duplicate processing when retries occur, your destination should treat Data Destinations delivery as at-least-once delivery and deduplicate incoming events using the unique Event ID.

• The destination executes time-consuming operations, such as synchronous database writes, complex computations, or downstream API requests, before returning an HTTP response.
• A service downstream from your handler experienced high latency or a timeout.
• High incoming event volume exhausted available server resources.

• Acknowledge incoming payloads immediately with an HTTP 2xx status code, offloading long-running operations to a background queue or worker process.
• Monitor your destination response latencies to identify transient slowdowns under load.
• Ensure your destination is sized appropriately for peak concurrency.

• 91300: Event delivery to destination failed
• 91306: Destination endpoint returned a server error
• 91307: Could not connect to destination endpoint

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