A duplicate request can keep reminders alive after completion
A duplicate request can keep reminders alive after completion
When a recipient reports reminders after completing a task, correlate the reminder's internal record identifier with the completed record before blaming terminal-state cancellation. A duplicate-warning override can create a second independently scheduled request for the same business reference and recipient. The first request may correctly cancel its reminders while the second continues. Trace creation, override, completion, and send events for both records. Resolve whether the second request is redundant before retiring it; matching contact details alone cannot establish that separate work is unnecessary. Application send logs also do not establish carrier delivery.
Applies when: Reminders continue despite a completed record and duplicate requests are possible. Keywords: duplicate request reminder completion cancellation scheduler record identity