Failed Records for Reverse ETL Syncs Beta

Until now, a Reverse ETL sync that completed with failures told you how many records failed, with one sampled error per status code. It now tells you why, for every record.

Open a completed sync and the Failed records panel shows a breakdown of failures by error code. Turn on Retain and show failures for the connection and the panel also lists every failed record with the exact error RudderStack recorded, and you can open any record to see its source row, read live from your warehouse. The complete set lands in your warehouse as a table you can query and join like any other.

See Failed records for details.

Key features

• Every failed record, with its error: The exact error RudderStack recorded, not just a status code or a single sample.
• Filter thousands of failures in one click: Cards break failures down by error code, and each is a filter.
• Source row alongside the error: Open any record to see the values RudderStack sent, pulled live from your warehouse.
• The full set in your warehouse: Each sync’s failed records land in a REJ_* table in the RudderStack schema, with a retention window you control.
• Audience syncs too: The same panel appears on audience sync pages.

Get started

1. Open a Reverse ETL connection and go to the Settings tab.
2. Turn on Retain and show failures and set the failure retention.
3. After the next sync, open it from the Syncs tab to see the failed records.

Capturing error details is a per-connection opt-in and applies from the next sync, so existing runs don’t fill in retroactively.