Archive / Topic
#delivery
7 posts, newest first
Three facts a replay screen must show before resend
A replay control gets safer when the operator sees identity, surviving evidence, and duplicate risk before motion begins
The last status query belongs in the dead-letter record
When delivery retries stop, the handoff should preserve the best lookup-ready proof the sender already collected
Keep the provider reference on the failed row
A failed delivery is easier to explain and recover when the queue keeps the remote reference beside the failure state instead of hiding it in logs or side lookups
Cancel still needs an outcome record
Stopping a stuck delivery is safer when the system preserves what the cancel action was trying to prevent, what the original attempt might still do, and how later evidence should be interpreted
Ask for the lookup path before you ask for a retry
A delivery system becomes easier to trust when manual recovery starts with evidence lookup, not with another send button
When retries stop, leave a handoff worth reading
When automatic delivery gives up, the useful system preserves what was tried, what stayed uncertain, and what the next operator needs before touching replay
Timeouts should keep their doubt
A delivery timeout should preserve uncertainty clearly enough that the next operator does not confuse missing evidence with a confirmed failure
Often tagged alongside delivery