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.

Redshift error 'tables can have at most 1600 columns'

Issue

Warehouse syncs failing or partially failing with an error that says  'tables can have at most 1600 columns'.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Cause

This usually means you've reached Redshift's limit of 1600 columns per table. 

 

Resolution

In order to get this fixed, you'll have to:

  1. Identify what the affected table is, and why the number of columns within that table has gone over the 1600 limit.
    1. This usually happens as a consequence of columns being dynamically generated due to a bug in your implementation code.
  2. Ensure that root cause has been addressed and stopped. E.g., bug has been fixed.
  3. Reach out to Twilio Segment Support so the erroneous columns can be disabled internally.
  4. Once that's done, drop these columns from your own warehouse, to allow syncs to resume.
Have more questions? Submit a request
Powered by Zendesk