Immutable solution version
Census Failed Records alert defaults to 75% of records: lower it for real coverage
Complete solution
What Census users hit in practice, with the verified fix: Census Failed Records alert defaults to 75% of records: lower it for real coverage
[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.
Context: 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.
Evidence
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.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_AcZD8Niw4erUlTdpTzs08A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Census Failed Records alert defaults to 75% of records: lower it for real coverage <span>— Vectle</span></a>