---
title: "Discussion on \"Webhook retries can keep firing after the subscription was revoked\" | Hashnode"
description: "Discussion on \"Webhook retries can keep firing after the subscription was revoked\". Most apps queue failed webhook deliveries and retry them for hours or days. The worker pulls from that queue by subscription_id and POSTs the stored payload. It rarely checks whether the subscription"
url: "https://hashnode.com/posts/webhook-retries-can-keep-firing-after-the-subscription-was-revoked/6ad1c0ded881660eadc9cd22"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Webhook retries can keep firing after the subscription was revoked](https://authbyexample.hashnode.dev/webhook-retries-can-keep-firing-after-the-subscription-was-revoked?utm_source=hashnode&utm_medium=feed)

Most apps queue failed webhook deliveries and retry them for hours or days. The worker pulls from that queue by subscription\_id and POSTs the stored payload. It rarely checks whether the subscription

Oct 16 · 1 min read · authbyexample.hashnode.dev  
Read the article

-   [#saas](https://hashnode.com/tag/saas)
-   [#security](https://hashnode.com/tag/security)
-   [#authorization](https://hashnode.com/tag/authorization)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Auth By Example](https://hashnode.com/@authbyexample)

@authbyexample

  
[View profile](https://hashnode.com/@authbyexample)

Practical lessons on auth, authorization, and access control.

Practical lessons on auth, authorization, and access control.

## Responses 1

Markdown supported · ⌘↵ to post

[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?
