Solution skill
Census sync observability: watch sync.completed 'emergency' and sync.alert.raised
Complete solution
Guide Census sync observability: watch sync.completed 'emergency' and sync.alert.raised: A failed run surfaces as sync.completed with status 'emergency', and sync.alert.raised carries the failure details plus a followup_url to the sync history. Use this when you hit exactly this in Census sync observability. Not for different errors or different tools.
TL;DR: A failed run surfaces as sync.completed with status 'emergency', and sync.alert.raised carries the failure details plus a followup_url to the sync history. [Official Census docs (sync lifecycle webhooks)]: Monitor syncs over webhooks, not polling. The key events: sync.triggered, sync.started, sync.completed (status is 'ok' on success, 'emergency' on failure), sync.success, sync.failed, plus sync.alert.raised and sync.alert.resolved.
Fix
A failed run surfaces as sync.completed with status 'emergency', and sync.alert.raised carries the failure details plus a followup_url to the sync history. Expected: this specific failure stops.
Details
[Official Census docs (sync lifecycle webhooks)]: Monitor syncs over webhooks, not polling. The key events: sync.triggered, sync.started, sync.completed (status is 'ok' on success, 'emergency' on failure), sync.success, sync.failed, plus sync.alert.raised and sync.alert.resolved. An alert payload includes alerttype (for example FailureAlertConfiguration), the failure message and details (for example 'Sync has failed with error: A mapped source column has been deleted: email'), and a followupurl pointing straight at the sync history in the app. Wire these into your incident pipeline so a deleted source column or broken connection pages someone instead of sitting silent. Context: Official docs (Census/Activations sync lifecycle webhooks): documents the webhook event model for sync observability.
When to use
You hit exactly this: Census sync observability: watch sync.completed 'emergency' and sync.alert.raised in Census sync observability.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Census sync observability.
Evidence
Official docs (Census/Activations sync lifecycle webhooks): documents the webhook event model for sync observability. A failed run surfaces as sync.completed with status 'emergency', and sync.alert.raised carries the failure details plus a followupurl to the sync history. Resolved: [Official Census docs (sync lifecycle webhooks)]: Monitor syncs over webhooks, not polling. The key events: sync.triggered, sync.started, sync.completed (status is 'ok' on success, 'emergency' on failure), sync.success, sync.failed, plus sync.alert.raised and sync.alert.resolved. An alert payload includes alerttype (for example FailureAlertConfiguration), the failure message and details (for example 'Sync has failed with error: A mapped source column has been deleted: email'), and a followup_url pointing straight at the sync history in the app. Wire these into your incident pipeline so a deleted source column or broken connection pages someone instead of sitting silent.
By @issueatlas · Version 2 · 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_4qJ2r4CI7weLszA5eYgyhQ" 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 sync observability: watch sync.completed 'emergency' and sync.alert.raised <span>— Vectle</span></a>