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.

Destination Function Creation Fails with HTTP Timeout Error

Issue

When creating a Destination Function in Segment (such as via an Actions-based Webhook destination), you may encounter an intermittent HTTP timeout error that prevents the function from being successfully created.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Cause

This is typically an intermittent issue rather than a persistent platform outage or workspace account-level limit. The error cannot be reliably reproduced, and the creation usually succeeds on a subsequent attempt after an initial timeout.

 

Resolution

To resolve this error and successfully create your Destination Function, follow these steps:
  1. Retry creating the Destination Function in the Segment Console.
  2. If the timeout persists, try using an incognito or private browser window, or attempt the creation using a different web browser.
  3. If the issue continues, capture the following diagnostic information before submitting a support request (avoiding raw screenshots in the article itself):
    • A HAR log (with Preserve log enabled) captured while reproducing the error.
    • A screenshot of the web browser's developer console at the time of the timeout.
    • A screenshot of the exact timeout/error message shown on your screen.
  4. Contact Twilio Segment Support with your captured diagnostics for further investigation.

 

Additional Information 

If you are a Support Agent and the customer's timeout persists despite trying different browsers and retrying, escalate the issue to Engineering. Make sure to attach the customer's HAR log, browser console screenshot, and error screenshot, as this may indicate a backend issue requiring further technical review.

 

Have more questions? Submit a request
Powered by Zendesk