Offer no Replay for a delivery to a deleted target (closes #387)
check / check (push) Successful in 3m21s

The event log offered Replay on a delivery whose target was deleted,
and the refusal told the operator to recreate the target and replay.
That cannot work: a recreated target is a new one the old delivery
does not name, so the replay is refused again. The Replay button is
now left off such a delivery, whose row already names the target as
deleted, and the refusal a page left open can still reach now points
to Resubmit, which sends the event to the webhook's currently active
targets.

Model: opus-5-5
This commit is contained in:
2026-10-02 23:52:19 +00:00
parent 22fa502638
commit 2927a95558
6 changed files with 54 additions and 5 deletions
+3 -1
View File
@@ -21,7 +21,9 @@ const (
// replayTargetDeleted reports a target that once existed and has
// since been deleted. Deletes are soft and deliveries carry no
// foreign key to the target row, so the history survives its
// target and this is the ordinary case for an old event.
// target and this is the ordinary case for an old event. The
// event log shows no Replay button for such a delivery, so only
// a page loaded before the delete reaches this.
replayTargetDeleted noticeCode = "replay-target-deleted"
// replayTargetMissing reports a target id that names no row at