Template
Make every selected record end in an explicit status bucket
A total should account for the awkward records too.
Before you use it
- Use when
- A batch summary lists successes but leaves it unclear what happened to the rest.
Keep this limit in mind
- Retries and duplicate inputs require a defined counting unit. Do not mix business identities, attempts and message counts in one equation.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Run and cutoff: [snapshot]. Selected identities: [total]. Applied: [applied]. Rejected: [rejected]. Pending: [pending]. Unaccounted: [unaccounted]. Next action for unresolved identities: [action].
Why it matters
Freeze the selected input population and assign each identity to one mutually exclusive status at a stated cutoff. Include pending and unaccounted states instead of hiding them inside success. This is population accounting; successful accounting is not proof that the resulting field values are correct.
An example
A 200-record run has 183 applied, 9 rejected and 8 pending. It is fully accounted for, but it is not 200 successful updates.
Check your result
The disjoint buckets reconcile to the selected population, and unresolved IDs are retrievable.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMake every selected record end in an explicit status bucket
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaReconcile what is missing and what should never have arrivedUseful with this idea
Follow an accepted job to its actual completion state
Evidence and sources
AWS DMS distinguishes validation-pending, failed, suspended and validated records rather than treating every transferred record as validated.
A population-accounting ledger can expose unaccounted records but cannot replace comparison of their actual values.
AWS DMS data validation · Validation states
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.