Preserve Webhook Processing Order in Make

An order may be packed and shipped within seconds. If two webhook runs overlap, the earlier update could finish last and overwrite the newer state.

Worked example

Two tested order transitions

Order = T-21
First received = version 7, Packed
Second received = version 8, Shipped
Expected final state = version 8, Shipped
Separate late-arrival test = version 7 arrives after version 8 and is ignored.

Steps

  1. Identify the updates that affect the same destination state and capture their event IDs or versions.
  2. Enable sequential processing for the webhook scenario. Send two test events in order and make the first update take longer.
  3. Verify that the second execution waits and that the destination finishes in the latest state. Inspect queue delays under a small synthetic burst.
  4. At the destination, still compare event versions. Reject a stale update when it arrives late, since processing arrival order cannot recover a sender's original order.

What to check

  • Measure queue time when one run waits on a slow service. Serializing the entire scenario can also delay unrelated orders.
  • Check duplicate events and use an idempotent update so retried deliveries do not create extra records.

View Make

References