Skip to content

Quarantine a malformed result payload without losing its context

Keep parsing failures separate from empty evidence and preserve a minimal diagnostic reference.

Guides

Quarantine a malformed result payload without losing its context — what should the operator record?

A parser failure can turn into a false empty table if a workflow catches the error and continues with an empty array. Quarantine the malformed representation and keep the originating context. The operator needs a supported recovery path, not a reassuring zero-row result that hides a processing failure.

Practical operations check
Keep parsing failures separate from empty evidence and preserve a minimal diagnostic reference.
Record payload_reference, parser_revision and the actual failure location without exposing sensitive content in a general diagnostic message. A diagnostic can name byte offset or field path when meaningful, but should avoid attaching the entire sensitive response to a broadly accessible error ticket.
State what caused the failure only when observed, and keep unresolved payload defects blocked rather than guessing missing content from nearby rows. The final state can say decoding fixed and schema still unresolved, showing that one successful repair does not automatically establish every remaining validation dimension.
01 / Guides

Capture the parse boundary

Record payload_reference, parser_revision and the actual failure location without exposing sensitive content in a general diagnostic message. A diagnostic can name byte offset or field path when meaningful, but should avoid attaching the entire sensitive response to a broadly accessible error ticket.

02 / Guides

Block empty fallback

Ensure a parse exception produces blocked-parse rather than an accepted empty evidence set or an automatically padded table. Ensure downstream code cannot interpret blocked-parse as valid empty membership; a missing parse result should remain an explicit gate failure in the output manifest.

03 / Guides

Inspect representation causes

Check truncation, encoding and expected envelope shape using a permitted copy, separating local format problems from unexpected returned structure. If the received file is truncated, distinguish that observed condition from an unsupported assertion about the upstream service returning malformed data in the first place.

04 / Guides

Recover through a new artifact

If a valid authorized representation is obtained, assign a new artifact revision and reconcile its membership against any previously accepted evidence. A repaired representation should never be assembled by guessing missing quoted text or copying a similar row; recovery needs a valid permitted input or remains blocked.

05 / Guides

Close with supported findings

State what caused the failure only when observed, and keep unresolved payload defects blocked rather than guessing missing content from nearby rows. The final state can say decoding fixed and schema still unresolved, showing that one successful repair does not automatically establish every remaining validation dimension.

Keep the boundaries clear.

  • Keep parsing failures separate from empty evidence and preserve a minimal diagnostic reference.
  • Operational record: Capture the parse boundary. 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