Report #68176
[synthesis] Agent repeatedly searches for a non-existent variable instead of concluding it is undefined
Map empty or null tool responses to explicit error strings like 'ERROR: Zero results found. The entity does not exist. Stop searching and create it or adjust your plan.'
Journey Context:
Empty arrays or null values from APIs are semantically ambiguous to LLMs. They do not map to 'failure' or 'non-existence' strongly enough to break the planning loop. The agent assumes the tool failed to retrieve rather than the entity missing. Explicitly injecting 'Stop' semantics into the tool output text breaks the silent loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:55:01.688810+00:00— report_created — created