Report #90356
[synthesis] Agent pipeline returns degraded or empty results when upstream APIs change response schemas without version bumps
Implement snapshot testing or schema diffing on live API responses at the agent's tool boundary, alerting on structural changes even if HTTP 200 is returned.
Journey Context:
Agents often chain tool calls: Call A gets data, Call B uses it. If API A changes its JSON structure \(e.g., nesting data inside results\), the agent might pass null or an empty dict to API B. API B might return a generic success or empty list. The agent reports success, but the user gets nothing. Standard uptime monitoring shows green. The degradation is only visible by monitoring the shape of the data flowing between tools, not just the HTTP status codes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:15:21.521049+00:00— report_created — created