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.

Linked Audience compute times running long in Engage

Question

What could cause Linked audience compute times to run long in Segment Engage? Audience runs are taking much longer than expected to complete.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Answer

Linked audience compute times in Segment Engage can run long if the destination is rate limited, especially when multiple audiences are syncing at the same time. For rate limited destinations, the limit is shared across all audiences linked to the same destination, so high-volume runs or simultaneous syncs can saturate the available bandwidth and cause delays. To improve performance, avoid triggering multiple audience runs at the same time. If you need to increase the rate limit of downstream destinations, please contact support.

 

Additional Information 

If you need to adjust the rate limit, ensure that the new value does not exceed the capacity of your destination system to prevent delivery failures or retries.

 

Have more questions? Submit a request
Powered by Zendesk