Skip to content

Triage a partial response without discarding accepted evidence

Separate valid returned rows, pending coverage and actual failures in an operational recovery ledger.

Guides

Triage a partial response without discarding accepted evidence — what should the operator record?

A partial response can still contain useful evidence, but it should not be relabeled complete when an operator saves the rows. Triage the response envelope and accepted membership separately. This preserves legitimate work while making the remaining gap visible to anyone preparing a table, export or handoff.

Practical operations check
Separate valid returned rows, pending coverage and actual failures in an operational recovery ledger.
Record the actual returned status and coverage notes alongside the admitted row identifiers and originating query reference. Preserve actual pending categories or explicit failures from the response, not an assistant-written guess about which platforms or record kinds probably remain incomplete.
State actual accepted membership and remaining unresolved scope without treating a successful recovery request as proof of exhaustive source coverage. Closeout should distinguish partial by operator choice from partial by source error, because the next safe action and the interpretation of missing records differ.
01 / Guides

Capture partial metadata

Record the actual returned status and coverage notes alongside the admitted row identifiers and originating query reference. Preserve actual pending categories or explicit failures from the response, not an assistant-written guess about which platforms or record kinds probably remain incomplete.

02 / Guides

Classify unresolved scope

Separate requested-but-unreturned categories, pending continuation and explicit errors using only conditions supported by the actual receipt. Requested categories with no returned rows can mean no admitted evidence so far; label the operational state without claiming that the underlying source contains no matches.

03 / Guides

Choose the next safe action

Use documented continuation when available or mark a bounded partial stop; do not launch a broader request merely to conceal the shortfall. If no documented continuation is available, a bounded partial handoff can be appropriate provided it retains the original request and clearly states the unmet requirement.

04 / Guides

Reconcile later evidence

If an authorized recovery returns more rows, attach its own receipt identity and compare overlaps before updating the working table. A recovered page with overlapping keys should contribute only justified new membership, while later observations of existing keys remain separately traceable to their own receipts.

05 / Guides

Close with bounded coverage

State actual accepted membership and remaining unresolved scope without treating a successful recovery request as proof of exhaustive source coverage. Closeout should distinguish partial by operator choice from partial by source error, because the next safe action and the interpretation of missing records differ.

Keep the boundaries clear.

  • Separate valid returned rows, pending coverage and actual failures in an operational recovery ledger.
  • Operational record: Capture partial metadata. 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