Aggregation failed
An aggregation task ended with errors or no data.
Aggregation failures stem from connector config, schema mismatches or credential problems. Read the task result for the specific error.
- Symptom: An aggregation task ended with errors or no data.
- Most likely causes
- Step-by-step fixes
- How to prevent recurrence
An aggregation task ended in error or returned no or partial data. Since aggregation feeds everything downstream, a silent aggregation failure quickly leads to stale, wrong governance, so it must be caught and fixed promptly.
Start here: read the evidence
Open the task result for the failed aggregation. It records counts, warnings and the specific error. The error text almost always points directly at the cause, connection, schema or credentials.
Likely causes, in order
- Connector misconfiguration, wrong host, port or options.
- Credential or permission problem, the service account cannot read the required data.
- Schema mismatch, the target schema changed and no longer matches the mapping.
- Delta misconfiguration, incremental aggregation missing or misreading the change marker.
How to fix it
- Read the task result for the exact error.
- Verify connector configuration and credentials.
- Confirm the account schema still matches the target.
- Run a full aggregation to rule out delta-specific problems.
- Re-run and confirm the expected account counts.
Preventing recurrence
Alert on aggregation task failures and on unexpected drops in account counts; keep schema mappings under change control so target changes are handled deliberately; and periodically run full aggregations to catch what delta misses.
Common pitfalls
- Guessing instead of reading the task/transaction result, which usually names the cause.
- Fixing the symptom, not the root cause, so it returns.
- Changing several things at once, so you cannot tell what worked.