# Backfill Scope Triage

## Summary

The `26401749356` reconcile run reported `27` mismatch objects out of `51`
monitored objects.

Backfill handling must be split by drift type.

## Safe First Batch: Missing-Only Objects

These objects have `missing_ids_count > 0` and `unexpected_extra_ids_count = 0`.
They are the best candidates for a fast targeted backfill dataset.

| Object | Priority | Missing IDs |
| --- | --- | ---: |
| Account | P0 | 1 |
| Contact | P0 | 1 |
| Lead | P0 | 822 |
| CampaignMemberStatus | P1 | 1 |
| Quote | P1 | 1 |
| OpportunityLineItem | P1 | 3 |
| Order | P1 | 1 |
| OrderItem | P1 | 1 |
| OpportunityContactRole | P1 | 1 |
| Opportunity_Product__c | P1 | 3 |
| Quote_Product__c | P1 | 1 |
| Order_Product__c | P1 | 1 |
| PoC__c | P1 | 1 |
| CampaignMember | P2 | 83620 |
| org__c | P2 | 128 |
| AccountShare | P2 | 4 |

## Not Backfill-Only: Extra-Only Objects

These objects do not need missing-row import. They need cleanup or allowlist
review instead.

| Object | Priority | Unexpected Extra IDs |
| --- | --- | ---: |
| User | P0 | 1 |
| Profile | P0 | 2 |
| Event | P2 | 26 |

## Not Safe For Blind Import: Mixed Drift

These objects have both missing IDs and unexpected extra IDs. They should not
be included in a blind first-pass backfill batch.

| Object | Priority | Missing IDs | Unexpected Extra IDs |
| --- | --- | ---: | ---: |
| Global_Arr_Forecast__c | P1 | 1236 | 1236 |
| Task | P2 | 592 | 2759 |
| TaskRelation | P2 | 566 | 2 |
| TaskWhoRelation | P2 | 1329 | 2 |
| EmailMessage | P2 | 89 | 5 |
| LeadHistory | P2 | 8660 | 6759 |
| LeadShare | P2 | 3711 | 416 |
| OpportunityShare | P2 | 4 | 1 |

## Practical Recommendation

The first production backfill dataset should start with:

1. P0 missing-only objects
2. P1 missing-only objects
3. selected P2 missing-only objects after volume review

Recommended initial caution:

1. `CampaignMember` is missing-only, but the volume is large (`83620`)
2. `Lead` is missing-only, but still large enough to justify a dedicated batch
3. mixed-drift objects should be handled in a separate repair track