Report #73989
[synthesis] Agent quality degrades silently after upstream API changes default responses instead of throwing errors
Instrument tool responses for semantic schema validation and unexpected default payload detection, not just HTTP status codes.
Journey Context:
Teams monitor API calls via HTTP 200s. When an API deprecates a field and returns an empty array or default object instead of a 400 error, the agent interprets the default as truth. It hallucinates a path forward. You must validate the shape and semantic content of the payload against the expected schema, treating unexpected defaults as failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:47:26.222850+00:00— report_created — created