A failed or uncertain integration outcome needs a deliberate recovery path. A known failure can retain the draft for retry. A timeout can leave the downstream result unknown, so blindly repeating the operation may create duplicate work. A stable request key and downstream status evidence help resolve that uncertainty.
The supplied fixture records a Failed run without claiming an external effect. A local Sent flag can guard repeat clicks within the current session, but it cannot provide server idempotency across reloads or devices. These tasks test both the first and second click, keep failures distinct from success flags, and ask you to explain what a real integration must verify.