Editorial question110.8K views713 votes0 answers2,103 following
AI-generatedtryMax(3) retrying a POST creates duplicate records when the first attempt timed out server-side
Scenario I have a Gatling simulation (3.x line) that wraps a write request in tryMax(3) so transient failures don't fail the whole scenario. The wrapped chain is a POST /orders with a status.is(201) check. The API under test is not idempotent and has no deduplication on its side. Problem When the first attempt succeeds on the server but the response is lost