If you notice certain fields not receiving data from a specific date onward, or if data replication unexpectedly stops for some fields, it may indicate a potential data discrepancy issue. However, before diving into investigation or troubleshooting, it's crucial to first confirm whether a discrepancy actually exists.
First To Go
To confirm whether a discrepancy exists, you will need to check the following things.
Please confirm that these fields contain non-Null values in your source data. The reason we ask is that Stitch will only create a column on your table downstream once at least one value is returned for that field. Empty column can not be replicated to the destination because stitch cannot identify what is the data type of this column.
When data is deemed incompatible by the destination, the record will be “rejected” and logged in a table called _sdc_rejected. What looks like missing data may actually be a compatibility issue. If you’re missing data, the first place you should look is in the _sdc_rejected table in the integration’s schema. Please refer to stitch documentation rejected-records-system-table for more info on this table and how to use it to troubleshoot.
Stitch will create the _sdc_primary_keys even if none of the tables in the integration have a Primary Key. Primary Key data will be added to the table when and if a table is replicated that has a defined Primary Key. This means it’s possible to have an empty _sdc_primary_keys table.
If the missing records were created very recently, or if Stitch is replicating a large historical data set, you may need to wait for an update of your data to be completed before they appear in your destination.
If you are not in all of above situations, please feel free to contact Support for further investigation or troubleshooting.
Related Content
To follow the standard procedures for data discrepancy issues, please kindly provide the relevant information according to our document here:
