# Troubleshooting Replication Issues

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.

## Common integration issues

[Missing Columns & NULL Values](https://help.qlik.com/en-US/stitch/troubleshooting/missing-columns-and-null-values) If you’ve noticed some missing columns or data from your data warehouse, the root cause may be `NULL` values.

[Non-Replicating Data & Unsupported Data Types](https://help.qlik.com/en-US/stitch/troubleshooting/non-replicating-data-unsupported-data-types) 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.

## Database integration issues

[Database Integration Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/database-extraction-error-reference) Extraction errors for database integrations and how to resolve them.

[Database Integration Table Name Collisons](https://help.qlik.com/en-US/stitch/troubleshooting/data-discrepancies/database-integration-table-name-collisions) In database integrations, if the names of multiple tables canonicalize to the same name - even if they’re from different source databases 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](https://help.qlik.com/en-US/stitch/troubleshooting/missing-mongo-data-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](https://help.qlik.com/en-US/stitch/troubleshooting/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](https://help.qlik.com/en-US/stitch/troubleshooting/mysql-tinyint1-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 Read Replicas and Slow Replication](https://help.qlik.com/en-US/stitch/troubleshooting/postgres-hot-standby-settings-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.

[Unable to Load Tables Due to Source Database Access Level](https://help.qlik.com/en-US/stitch/troubleshooting/too-many-tables-to-load-database-integration) 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](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/common-saas-extraction-error-reference) Extraction errors applicable to all SaaS integrations and how to resolve them.

[Google Sheets Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/google-sheets-extraction-error-reference) Extraction errors for Google Sheets integrations and how to resolve them.

[Intercom Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/intercom-extraction-error-reference) Extraction errors for Intercom integrations and how to resolve them.

[Missing Segment Data & Selective Integration Snippets](https://help.qlik.com/en-US/stitch/troubleshooting/missing-segment-data-selective-integration-snippet) 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](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/netsuite-suitetalk-extraction-error-reference) Extraction errors for NetSuite integrations and how to resolve them.

[Pardot Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/pardot-extraction-error-reference) Extraction errors for Pardot integrations and how to resolve them.

[Salesforce Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/salesforce-extraction-error-reference) Extraction errors for Salesforce integrations and how to resolve them.

[Salesforce Replication & Selecting Too Many Columns](https://help.qlik.com/en-US/stitch/troubleshooting/salesforce-replication-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](https://help.qlik.com/en-US/stitch/troubleshooting/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.