Census Failed Records alert defaults to 75% of records: lower it for real coverage

TL;DR: Set alert frequency to First Violation to avoid alert fatigue. [Official Census docs (sync alerts)]: Each sync has six alert types: Failed Sync and Failed Records (both on by default), Sync Status, Full Sync Triggered, Sync Runtime, and Record Count Deviation. The gotcha: Failed Records alerts only when 75% of records are invalid in the source or rejected by the destination by default, so a sync can quietly drop thousands of records.

Census Failed Records alert defaults to 75% of records: lower it for real coverage

Fix

1. Set alert frequency to First Violation to avoid alert fatigue. Expected: this specific failure stops.

2. Failed Records defaults to alerting only when 75% of records are invalid or rejected, which is far too lenient for most pipelines; lower it or set it to any-record for critical syncs. Expected: this specific failure stops.

Details

[Official Census docs (sync alerts)]: Each sync has six alert types: Failed Sync and Failed Records (both on by default), Sync Status, Full Sync Triggered, Sync Runtime, and Record Count Deviation. Lower the threshold, even to any-record, for syncs you care about. Full Sync Triggered alerts tell you why a full sync ran, Sync Runtime fires when a sync runs long, and Record Count Deviation catches unexpected drops against the running average.

When to use

You hit exactly this: Census Failed Records alert defaults to 75% of records: lower it for real coverage in Census Failed Records.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Census Failed Records.

Root cause

The gotcha: Failed Records alerts only when 75% of records are invalid in the source or rejected by the destination by default, so a sync can quietly drop thousands of records.

Edge cases

• Context: Official docs (Census/Activations sync alerts): documents the six alert types and the gotcha that catches teams.

Official docs (Census/Activations sync alerts): documents the six alert types and the gotcha that catches teams. Failed Records defaults to alerting only when 75% of records are invalid or rejected, which is far too lenient for most pipelines; lower it or set it to any-record for critical syncs. Resolved: [Official Census docs (sync alerts)]: Each sync has six alert types: Failed Sync and Failed Records (both on by default), Sync Status, Full Sync Triggered, Sync Runtime, and Record Count Deviation. The gotcha: Failed Records alerts only when 75% of records are invalid in the source or rejected by the destination by default, so a sync can quietly drop thousands of records. Lower the threshold, even to any-record, for syncs you care about. Full Sync Triggered alerts tell you why a full sync ran, Sync Runtime fires when a sync runs long, and Record Count Deviation catches unexpected drops against the running average. Set alert frequency to First Violation to avoid alert fatigue.