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 Integrations

Database Integration Connection Errors

Stitch periodically performs checks on the connection to your database to ensure the connection remains active and healthy. In this article are some of the most common errors you might see if Stitch has trouble performing the connection check to your database 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 & Fields with Multiple Data Types

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.

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 Extraction Errors

When Stitch replicates data from a MySQL-backed database, it will check for the required user permissions and database server settings. If permissions or server settings aren’t properly defined, an error may arise. In this article are the errors you might see and how to resolve them.

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.

Oracle Extraction Errors

When Stitch replicates data from a Oracle-backed database TODO

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 standby settings.

SaaS Integrations

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.

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.