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.

Reverse ETL: Troubleshooting Model Previews Failing to Update or Refresh

Issue

Customers report that their Reverse ETL model preview is not updating or refreshing in the Segment workspace after making schema changes or adding new warehouse columns. Because the preview shows outdated data, the newly added properties are missing and unavailable for selection when attempting to create or edit mappings

 

Product

Twilio Segment

 

Environment

Segment Console

 

Cause

This issue occurs because Segment uses a caching system that stores previously generated preview results to speed up the interface. When you update the table definition directly in your data warehouse (such as adding or modifying columns), Segment might not automatically detect these changes. As a result, the system continues to serve the old, cached preview data instead of fetching the new columns.

 

Resolution

To resolve this issue and ensure the most up-to-date data is available for your mappings, you need to force the system to fetch fresh data from your source:

  1. Navigate to your Reverse ETL source and open the Model Query Builder within the Segment Workspace.
  2. Locate the "Use Latest Data" option (typically found in the Data Settings area of the builder).
  3. Toggle or check the "Use Latest Data" option. This forces Segment to bypass the cached preview data and fetch the latest schema and data from your warehouse.
  4. Save your changes to ensure the most recent data is used in future model query executions.

 

Additional Information 

If you do not see the "Use Latest Data" option or the preview is still stuck, you can artificially trigger a cache refresh by making a non-meaningful change to your SQL query. For example, simply adding an extra space somewhere in the query will invalidate the cache and force a fresh preview response.

Have more questions? Submit a request
Powered by Zendesk