SUMMARY: When confirmation fails, the sender may not know whether the receiving service acted. A repeat attempt should not automatically become another appointment, case or obligation.
Name What Is Repeated
In The Second Receipt, a fictional station creates a case for each arrival. Its records count deliveries correctly but misrepresent one request as two separate intentions.
Distinguish an intended operation from its delivery attempts and from the resulting work. An explicit operation reference can help connect attempts, provided its scope and handling rules are defined. A reference is evidence within a process, not a universal guarantee that two actions are equivalent.
Similarity Is Not Identity
Two people can submit identical wording. One person can make similar requests for different dates. Conversely, a retry may contain harmless formatting changes. Merging solely by text, name or proximity in time can suppress legitimate work.
Define what constitutes a new request and what happens when a repeated reference accompanies changed information. Ambiguous cases need clarification or review rather than an invisible guess. Any technical implementation should be tested against the actual service contract.
Reconcile Consequences, Not Just Rows
Finding two related records does not establish that their downstream actions have been reconciled. One may already have issued an appointment while the other requested additional information. Identify those consequences before declaring the duplication resolved.
Preserve relevant receipt history under an appropriate retention policy. Record which case owns the next step, explain the relationship to affected users, and avoid resetting an established waiting period merely because delivery was repeated.
Make Uncertainty Visible
A helpful confirmation can distinguish an existing request found, a new request created and a result that remains uncertain. Do not promise success when the service has only accepted a retry for investigation.
Use Test a Lost Confirmation within the systems accountability guide. This is a conceptual workflow review, not a production implementation recipe or advice about contractual obligations.