GUIDES · BETSLIP DOCTOR
Why should retrying a notification not revive a deleted source action?
Because retrying notification work is not the same as recreating the source action. A retry should be checked against the current source and its revision; if that source is gone or no longer matches, the old notification should not bring it back.
For BSD readers handling this notification task · Updated
A retry repeats processing, not the original action
A notification points to a source action. It does not own that action or have permission to recreate it. In BSD’s notification contract, source identifiers are references and the current source must be rederived when the notification is processed. The receipt can describe outcomes such as replayed, suppressed, or gone; those states are different from making a new club reply or like.
That distinction protects the meaning of the inbox. If someone removed an action, replaying an older request should not make it look as though the person acted again.
The source must still match
A reply or like can change after its notification was first queued. The notification carries source revision information so processing can compare the saved reference with the current discussion or reaction. BSD’s open flow also reloads the notice and checks current club access, approved status, and source revision before choosing its destination.
If those checks no longer match, treat the old item as unavailable or changed. Do not read a retry receipt as proof that the original action has been restored.
Follow the current discussion
If an old notice cannot open, use the current Tail community view and look only at discussions you can access now. A retry should not bypass club access, restore a deleted post, or turn an old revision into fresh activity. This guidance covers recorded free-club reply and like notifications only; it makes no claim about other notification types or external alerts.
A removed reaction and an old notice
Imagine a member receives a notice about a like on a free-club post. The liker removes that reaction before the notice is retried. The retry should be judged against the current reaction state; it should not make the removed like appear again as a new action.
Related questions
Does retrying a notification repeat the like or reply?
No. Notification processing refers to an existing source action. It should not create a second social action.
What if the old target no longer opens?
The source may have changed or become unavailable. Check the current club discussion only if your access still permits it.