Purpose
This article helps troubleshoot scenarios where the ID_Graph orchestration output contains significantly fewer rows than usual, even though the workflow completes successfully.
Scope
This article applies to:
CRM ingestion workflows
ID Graph delta (incremental) outputs
Successfully completed workflows with unexpected row count drops
Symptoms
You may observe one or more of the following:
ID_Graph Orchestration row count is much lower than previous days
Workflow status shows Completed Successfully
No query execution or destination errors
Output file is delivered but contains fewer records
How CRM_ID_Graph_Delta Orchestration Works
CRM_ID_Graph_Delta is an orchestration that generates incremental (delta) ID Graph outputs
It processes CRM source data and publishes only new or updated records
Amperity uses idempotent upserts- Records that already exist and have not changed are not re-inserted
Because of this design, daily row counts may vary.
Common Causes
1. Fewer Net-New or Updated CRM Records
If the CRM source system sends fewer new or updated records on a given day, the delta output will naturally be smaller.
2. Duplicate or Re-sent Data
Re-sending unchanged data will not increase the delta output due to idempotent processing.
3. CRM Export Data Quality Issues
Issues such as:
Unexpected special characters
Formatting inconsistencies
Partially malformed records
can reduce the number of records successfully ingested without causing workflow failures.
Step-by-Step Troubleshooting
Step 1: Confirm Workflow Completion
Verify the CRM workflow completed successfully
Confirm the CRM_ID_Graph_Delta orchestration executed in the expected workflow run
Step 2: Review Orchestration Output
Open the CRM_ID_Graph_Delta orchestration
Review the most recent run details
Confirm the row count matches the delivered output
Step 3: Review CRM Source Data Changes
Check how many CRM records were new or updated for the affected date
Compare against previous days to identify drops in source changes
Step 4: Inspect the CRM Export File
For the affected date:
Compare row counts with prior files
Validate file completeness
Check for formatting or character issues
Step 5: Confirm Backfill or Replay Behavior
Determine whether data was re-sent without changes
Unchanged backfill data will not appear in delta outputs
Expected Resolution
Once the CRM export contains the expected number of new or updated records, the CRM_ID_Graph_Delta orchestration output should return to normal volumes in the next successful workflow run.
No platform configuration changes are usually required.
When to Contact Support
Contact Amperity Support if:
The workflow fails or does not complete
Source data appears correct but delta output remains low across multiple runs
You are unable to validate CRM export behavior
Summary
CRM_ID_Graph_Delta is an orchestration, not a standalone query
Low row counts usually reflect source data changes, not platform issues
Idempotent upserts prevent duplicates from appearing in delta outputs
Most cases can be resolved by reviewing CRM export data