Skip to content

Reconcile overlapping rows after a page retry

Handle retry duplicates without discarding new evidence or inflating accepted counts.

Guides

Reconcile overlapping rows after a page retry — what should the operator record?

A timeout can leave uncertainty about whether a page was received or appended. Retrying may produce overlapping identifiers, and blindly appending them inflates the table. Separate receipt history from admitted membership so the retry can be explained while each eligible evidence object appears only once in the working view.

Practical operations check
Handle retry duplicates without discarding new evidence or inflating accepted counts.
Record the last known committed receipt before retrying; do not infer success merely because the client stopped showing a loading indicator. A ledger marker received without committed means the response may exist but membership admission is unfinished; inspect that distinction before issuing another request.
Report accepted unique records separately from received rows and note whether the uncertain original append was resolved through the ledger. The closeout can report received rows and unique admitted keys separately; both are operational measurements and neither estimates the total available source population.
01 / Guides

Freeze the append state

Record the last known committed receipt before retrying; do not infer success merely because the client stopped showing a loading indicator. A ledger marker received without committed means the response may exist but membership admission is unfinished; inspect that distinction before issuing another request.

02 / Guides

Inspect the retried receipt

Attach a retry_of reference when justified by the actual request context and retain the new response's own coverage state. If the original receipt never arrived, say retry context uncertain instead of inventing a receipt reference solely to make the chain appear neatly linked.

03 / Guides

Compare source keys

Classify rows as previously accepted, new or identity-unresolved using context-qualified identifiers, not text similarity or a repeated author name. A repeated source key with changed text is a field conflict to review, not automatically a new evidence object or an error to erase.

04 / Guides

Append only admitted differences

Add new records once, keeping field conflicts in an exception table rather than letting the retry overwrite the first observation silently. For each admitted key, keep the chosen observation reference and the reason for preferring it, preserving meaningful conflicts when current policy allows their retention.

05 / Guides

Close the retry incident

Report accepted unique records separately from received rows and note whether the uncertain original append was resolved through the ledger. The closeout can report received rows and unique admitted keys separately; both are operational measurements and neither estimates the total available source population.

Keep the boundaries clear.

  • Handle retry duplicates without discarding new evidence or inflating accepted counts.
  • Operational record: Freeze the append state. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage