Warehouse Errors

This is a permissioning issue. To learn how to set up proper permissions, you can check out our Postgres and Redshift guides.

This error occurs when your cluster is currently resizing. The warehouse will continue on its scheduled run interval - once the resize is complete, we'll load all data from the failed run.

This is a Redshift 500 - an internal server error. This is usually caused by having too many tables or too many columns. If you're seeing this error, contact the Segment Support team.

This is a networking error that typically arises when Redshift doesn't close properly close the connection or gets rebooted.

If you see this error on consecutive syncs, contact us.

This is a permissioning issue. To learn how to set up proper permissions, you can check out our postgres and redshift guides.

This is a credential issue. To fix your credentials, head over to Warehouse > Settings > Connection.

This is a credential issue. To fix your credentials, head over to Warehouse > Settings > Connection.

This is a networking error. The connection times out because Redshift doesn't close properly or gets rebooted.

If you see this error on consecutive syncs, contact us.

This occurs when a Postgres database is incorrectly connected as Redshift. To resolve this, delete the warehouse and reconnect, using the Postgres set up option.

This error is generally a network error when Redshift closes the connection. If the problem persists on multiple runs, contact us.

This is a permissioning issue. To learn how to set up proper permissions, you can check out our postgres and redshift guides.

This error is generally a network error when Redshift closes the connection. If the problem persists on multiple runs, contact us.

This error indicates that a column that is attempting to sync has the same title as a reserved keyword in Snowflake. More information regarding Snowflake's reserved keywords can be found in Snowflake's docs.