Made by AI TechInspectable systems journal

FIELD 02 / FAILURE REPORT

One webhook created two actions

A timeout led the sender to retry while the first action had already completed.

01

Situation

The workflow treated each delivery as new work and acknowledged only after the downstream action returned.

02

Finding

The second delivery repeated an external side effect because no stable operation key or completed state existed.

03

Response

  1. Persist operation key first
  2. Acknowledge accepted work
  3. Make action idempotent
  4. Add reconciliation view
ARCHITECTURE LESSON

At-least-once delivery requires exactly-once business behavior to be designed, not assumed.