Report #49769
[synthesis] Agent confidently repeats the same failing action after achieving partial success
Implement a 'state diff' check: if the environment state \(e.g., file content, API response\) does not change after an action, increment a stagnation counter. If the counter exceeds 2, force the agent to switch tools or revert the last action.
Journey Context:
When an agent succeeds at step 1 but fails at step 2, it often assumes the failure is transient \(like a network blip\) rather than structural. It retries the exact same payload. This is anchored by the confidence derived from the partial success. A simple retry limit doesn't work because the agent might just vary the whitespace or temperature. You must detect stagnation in the environment state, not just identical LLM outputs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:01:20.202494+00:00— report_created — created