If you’re having trouble getting Stitch to replicate or load some of your data, this is where you’ll find the resources to pinpoint and resolve the issue.
If you’ve noticed some missing columns or data from your data warehouse, the root cause may be
If a table isn’t replicating into your data warehouse, it may be because one or more of the columns in the table contains an unsupported data type.
Missing some Mongo data? The root cause may be multiple data types in the Replication Key field and how Mongo sorts data based on data type.
If you don’t see all the fields you expect to in the Replication Key field for you Mongo integration, the root cause may be insufficient permissions or a lack of field indexing.
If you’ve noticed that some MySQL
TINYINT(1) columns are displaying as
BIT in Stitch, it’s usually due to how the MySQL driver converts this data type.
If you connected a PostgreSQL read replica as a database integration and are experiencing extremely slow replication, the root cause may be the database’s
If you’ve noticed some missing data from your Segment integration, the culprit might be the selective integration snippet on your website.
If you’ve noticed some out-of-date Salesforce data in your data warehouse, the root cause may be a formula field.
If you received an error notification from Stitch about writing to your data warehouse, that means we ran into an issue loading your data. There can be a variety of reasons for this, each of which is specific to the type of destination you’re using.
Received an error about Stitch loading data into your Postgres data warehouse? Check out these common errors and how to resolve them.
Received an error about Stitch loading data into your Redshift data warehouse? Check out these common errors and how to resolve them.
If you’ve received a ‘Dependent Views’ error for your Redshift or Panoply data warehouse, you may need to temporarily drop dependent objects.