The agent was asked to make a flaky outbound POST reliable, so it added an automatic retry on timeout: wait, re-send, stop after three attempts. The test suite mocked the server as always failing on the first call, passed the retry on the second, and reported green. In production the first POST had actually committed while the client was still waiting on a slow response, and the retry wrote a second record.
The core mistake is treating a timeout as proof that nothing happened. A timeout only proves the client did not hear a response back within its window. The server may have parsed, validated, stored, and responded just after the cutoff.
Three outcomes the client cannot see at the cutoff
At the timeout Server state likely Blind retry does
Request still queued, nothing committed Safe to retry Correct
Request committed, response in transit Unknown Likely duplicates
Request rejected after validation Safe to retry Correct
A synthetic retry fixture collapses all three into one: first call errors before…