Detect an incomplete export file before distribution — what should the operator record?
An export can look plausible even when a transfer stops midway or a later page never arrives. Check structure and intended membership before opening it for wider use. Distinguish a broken local file from a valid partial response, because the recovery action and the wording of the handoff differ.
Use parse, envelope and membership checks to identify interrupted or partial result downloads.
Record file length, received time and any actual transfer failure without assuming that a small file must be incomplete. An empty export with a valid envelope can be legitimate; file length should trigger investigation, not determine a diagnosis without parsing and scope reconciliation.
Mark an unreconciled artifact incomplete with the actual failure reason; distribute only the checked revision and its supported coverage statement. The handoff should name whether the blocker is malformed structure, unmatched membership or unresolved transfer state so the receiver can choose the correct recovery action.Capture the artifact state
Record file length, received time and any actual transfer failure without assuming that a small file must be incomplete. An empty export with a valid envelope can be legitimate; file length should trigger investigation, not determine a diagnosis without parsing and scope reconciliation.
Parse the full representation
Use a format-aware reader through the final record; a JSON prefix or the first spreadsheet screen is insufficient evidence of a complete file. For CSV, verify logical records through the parser rather than counting newline characters, since embedded line breaks can occur inside quoted evidence text fields.
Check expected boundaries
Compare parsed identifiers and returned coverage against the intended export scope, keeping a valid short response separate from a parse failure. Compare expected export membership from an authorized manifest, not a requested target count that the original response may never have satisfied in the first place.
Recover within authorization
If a new download is allowed, retain a new artifact revision and reconcile it against the same permitted scope rather than stitching arbitrary byte fragments. A fresh download can reflect current access changes; keep it as a new artifact and explain differences instead of assuming it must reproduce the earlier file bytewise.
Block ambiguous delivery
Mark an unreconciled artifact incomplete with the actual failure reason; distribute only the checked revision and its supported coverage statement. The handoff should name whether the blocker is malformed structure, unmatched membership or unresolved transfer state so the receiver can choose the correct recovery action.
Keep the boundaries clear.
- Use parse, envelope and membership checks to identify interrupted or partial result downloads.
- Operational record: Capture the artifact 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.