Report #38298
[synthesis] Agent confidently proceeds after silent API failures causing null data corruption
Enforce strict schema validation on tool outputs; treat missing or null keys as hard stops requiring explicit user/agent clarification before proceeding.
Journey Context:
When an API returns an error JSON or empty data, agents often parse the response optimistically, extracting a null or empty string. This null propagates to the next step \(e.g., a database delete command filtering on id = null\), wiping data. Agents lack the intrinsic 'surprise' humans feel at an empty result. You must force a hard failure on structural anomalies rather than letting the agent assume success.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:45:46.261045+00:00— report_created — created