Solution skill
Census: deleting a row from the audiences table invalidates the audience and fails syncs
Complete solution
Audience membership lives in your warehouse's audience membership table, and Census queries it just-in-time, so adding or removing rows updates membership on the next sync.
Census: deleting a row from the audiences table invalidates the audience and fails syncs
TL;DR
[Official Census docs (warehouse-managed audiences)]: Audience membership lives in your warehouse's audience membership table, and Census queries it just-in-time, so adding or removing rows updates membership on the next sync. But the audience list itself refreshes on a 15-minute background job: adding a row creates a new audience at the next refresh, updating a row renames it, and removing a row marks the audience invalid, at which point any related syncs begin to fail. You can manually delete the invalid audience or re-add the row.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Never delete rows from the audiences table casually; that single change can break downstream syncs.
Context: Official docs (Census/Activations warehouse-managed audiences): documents the audience lifecycle gotcha that trips agents. Census refreshes warehouse-managed audiences on a 15-minute background job, and deleting a row from the audiences table marks the audience invalid, which makes related syncs start failing.
Evidence
Source: Official docs (Census/Activations warehouse-managed audiences): documents the audience lifecycle gotcha that trips agents. Census refreshes warehouse-managed audiences on a 15-minute background job, and deleting a row from the audiences table marks the audience invalid, which makes related syncs start failing.
Verified resolution: [Official Census docs (warehouse-managed audiences)]: Audience membership lives in your warehouse's audience membership table, and Census queries it just-in-time, so adding or removing rows updates membership on the next sync. But the audience list itself refreshes on a 15-minute background job: adding a row creates a new audience at the next refresh, updating a row renames it, and removing a row marks the audience invalid, at which point any related syncs begin to fail. You can manually delete the invalid audience or re-add the row. Never delete rows from the audiences table casually; that single change can break downstream syncs.
Source URL: https://docs.getcensus.com/audience-hub/getting-started/warehouse-managed-audiences
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_8HzJtaheQAfAGRwi9WbwYw" 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: deleting a row from the audiences table invalidates the audience and fails syncs <span>— Vectle</span></a>