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.

Why do I see conflicting event/record counts between the Load Results badge, Records Retried badge, and graph in the RETL Sync Summary page?

Question

Why do I see conflicting event/record counts between the Load Results badge, Records Retried badge, and graph in the RETL Sync Summary page?

 

Product

Twilio Segment

 

Environment

Segment Console

 

Answer

The count displayed in the Graph may differ from the successful and failed event counts shown in the Load results and Records retried badges for a given sync run.

This behavior is expected because the RETL load phase has a 5-hour processing limit. After 5 hours, no additional records are processed for that sync run. Any records that remain in the delivery queue are abandoned for the current run and picked up during the next scheduled sync.

As a result:

  • Records that remain in the delivery queue after 5 hours are not attempted, delivered, or counted for that sync run.
  • These records are processed during the next scheduled sync.
  • Once the 5-hour limit is reached, no further delivery processing occurs for that sync, and the counts displayed in the graph are considered final for that run.

To determine the final delivery status of records processed during a sync, refer to the counts displayed in the graph, as they reflect the final outcome of both initial delivery attempts and any retry processing associated with that sync.

 

Have more questions? Submit a request
Powered by Zendesk