Having trouble connecting your database or SaaS integration? Investigating a data discrepancy? Here you’ll find resources for some of the most common causes of connection troubles and data discrepancies related to integrations.
Common integration issues
Known Third-Party Issues Occasionally, some integrations used by Stitch may encounter bugs or other issues. Whenever we’ve identified a third-party issue - meaning on the integration provider’s end - we’ll post an update here.
Re-authorizing Integrations If you see a message that asks you to re-authorize an integration, it means that Stitch’s permissions to that service have been revoked.
Third-Party Integration Downtime From time to time, some of the applications and databases we integrate with may experience downtime. During these outages, Stitch may be unable to successfully connect to your data source and replicate your data.
Database integration issues
Database Integration Connection Errors Resolve errors related to connecting to a database integration.
Database Integration Extraction Error Reference Extraction errors for database integrations and how to resolve them.
Database Integration Table Name Collisons In database integrations, if the names of multiple tables canonicalize to the same name - even if they’re from different source databses or schemas - name collisions and data discrepancies can occur. This applies to any database integration available in Stitch.
Missing Mongo Data Due to Fields with Multiple Data Types Missing some Mongo data? The root cause may be multiple data types in the Replication Key or Primary Key (_id) fields.
Mongo Fields Missing from Replication Key Menu 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.
MySQL TINYINT(1)/boolean Columns Stored as BIT
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.
PostgreSQL Data Types Stored as Strings
When certain Postgres data types are replicated, they’ll be stored as
strings in your data warehouse.
PostgreSQL Read Replicas and Slow Replication
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
Unable to Load Tables Due to Source Database Access Level Mitigate issues with tables displaying in the Tables to Replicate tab by limiting the authorizing database user’s access to source tables.
SaaS integration issues
Common SaaS Integration Extraction Error Reference Extraction errors applicable to all SaaS integrations and how to resolve them.
Google Sheets Extraction Error Reference Extraction errors for Google Sheets integrations and how to resolve them.
Missing Segment Data & Selective Integration Snippets If you’ve noticed some missing data from your Segment integration, the culprit might be the selective integration snippet on your website.
NetSuite Extraction Error Reference Extraction errors for NetSuite integrations and how to resolve them.
SaaS Integration Connection Errors If Stitch is unable to connect to one of your SaaS integrations, the issue may be a security setting on the integration provider’s side.
Salesforce Replication & Selecting Too Many Columns If a single Salesforce object has a large number of columns set to replicate, issues with replication may arise.
Stale Salesforce Data & Formula Fields If you’ve noticed some out-of-date Salesforce data in your data warehouse, the root cause may be a formula field.