A city FDM object-create POST times out; the client cannot tell whether the firewall object was created. Which approach is the robust default for that non-idempotent write?
Select an answer to reveal the explanation.
Short Explanation
A create that went silent may already be filed at city hall. Blindly mailing a second form can invent a duplicate. Mark it uncertain—confirm, key it, or escalate—don't always retry POST.
Full Explanation
Timeouts on non-idempotent POSTs are unsafe to retry blindly because the server may have committed. Robust handling uses idempotency keys, a confirming GET when the API allows, or failing that unit for operator follow-up. Blind POST retries risk duplicate objects; removing timeouts only hides the problem.