From time to time, Stitch may run into problems when attempting to load data into your data warehouse. When data is deemed incompatible by the data warehouse, the record will be "rejected" and Stitch will log it in a rejected records log.
In this article, we’ll cover:
Reasons for rejection will depend on the type of data warehouse you’re using, as each has its own data requirements and restrictions. For a detailed rollup of how each destination handles data - including what situations will result in rejected records - refer to the Expected Data Loading Behavior doc for the destination you’re using:
There are some common causes for rejection, however:
__bigint), which are reserved by Stitch
_rjmprefixes, which are reserved by Stitch
In every integration schema created by Stitch is a table called
_sdc_rejected which acts as a log for rejected records.
This table contains information about why a record was rejected, the date of the rejection, and the table in the integration schema that the data was destined for:
|_sdc_rejected_at||The date of the load error|
|table_name||The table the record was destined for|
|reason||The reason for the rejection|
|record||The raw Transit data of the record|
Here’s an example of what an
_sdc_rejected table might look like:
||Column names from client should not include reserved datatype suffix on name
||Field collision on
Why were these records rejected? Here are the details:
name__bigint. Stitch reserves these suffixes for column names, so any column name containing a data type suffix will be rejected.
In some cases, you may be able to pinpoint and resolve the root cause of the rejection. Here’s an example:
userstable that contains two fields that differ only by case:
first_order_id) in the source database and re-sync the data.
Note that it may not be possible to resolve every rejected record issue. While you may be able to resolve the issue in a database integration, the majority of SaaS integrations don’t provide users with the ability to define and control the structure of their data.