Imagine an order notification arriving twice. The first delivery opened a review task. A connection failed before the sender got its acknowledgement, so the notification arrived again. The second copy looks urgent too. Your neat new assistant now has two opportunities to do the same work.
We would test that repeat before adding more intelligence to the queue. A beautifully written second response is still a second response.
Two deliveries, one intended outcome
Shopify’s current developer guidance says webhook deliveries can repeat after timeouts or retries. It recommends processing that can be repeated without changing the outcome. Its documentation distinguishes the identifier used to detect duplicate deliveries from the identifier used to correlate deliveries arising from one merchant action. Those are different jobs; the implementation has to preserve the distinction.
Source: https://shopify.dev/docs/apps/build/webhooks/verify-deliveries
Here is a fictional rehearsal for an internal review queue. A notification called D17 starts one task, R42. The task is completed, and its result is recorded. Deliver the same D17 notification again.
The expected result is still one completed task, R42, with the repeated delivery recorded against it. A fresh task would be the wrong result for this rehearsal. Nothing here requires a live order edit, message or refund; use an invented notification and a local record.
Now change the starting condition. D17 was received, but the first attempt stopped before completing R42. A note saying “seen” is not evidence that the job finished. The repeat should lead the reviewer to the unfinished task and its known state, rather than silently declaring it complete. If the outcome is uncertain, record that uncertainty before deciding whether to retry the action.
Keep three questions apart
Did the notification arrive? Did processing start? Is the intended result confirmed?
Put the delivery reference, task reference, current state and result evidence on one row. Give a genuinely new notification its own review, even if it mentions the same order. Suppressing everything with the same order number would hide later work that actually needs doing.
This extends the support-queue lesson: the packet must tell the next person what happened, not merely attach a label.
https://www.rebuildshow.com/p/shopify-the-ticket-is-classified
Take one fictional completed task and repeat its notification. Then repeat one whose outcome is unresolved. Write the expected result for each before running the rehearsal. Compare the task records afterwards, not just the assistant’s wording.
The Rebuild Editorial


