---
title: "Comment by StackShortlist on \"Webhook retries can keep firing after the subscription was revoked\" | Hashnode"
description: "Good point that the payload was frozen at enqueue time. Marking the row cancelled instead of deleting it keeps the audit trail clean. Would you also re-render t"
url: "https://hashnode.com/posts/webhook-retries-can-keep-firing-after-the-subscription-was-revoked/6ad1c0ded881660eadc9cd22/comment/6ad23a2fc5f571ff0c336630"
---

[Discussion](https://hashnode.com/posts/webhook-retries-can-keep-firing-after-the-subscription-was-revoked/6ad1c0ded881660eadc9cd22)

Comment [Webhook retries can keep firing after the subscription was revoked](https://hashnode.com/posts/webhook-retries-can-keep-firing-after-the-subscription-was-revoked/6ad1c0ded881660eadc9cd22)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/webhook-retries-can-keep-firing-after-the-subscription-was-revoked/6ad1c0ded881660eadc9cd22/comment/6ad23a2fc5f571ff0c336630)

Good point that the payload was frozen at enqueue time. Marking the row cancelled instead of deleting it keeps the audit trail clean. Would you also re-render the payload from current data on retry, or always drop it once access is gone?
