Business-Deadline Webhooks: Durable Outbox and Idempotent Retries for SaaS Queues
Delayed webhook reminders should be modeled as durable delivery records with a due time, dispatched through a delayed task queue. The article argues that the queue controls when attempts happen, while the application database controls whether an attempt may change business state. Renewal events and outbox rows are written in one transaction, so committed reminders can be rediscovered after publishing or worker failures. The public HTTPS endpoint must claim each stable delivery ID under a uniqueness constraint, so repeated transport attempts do not repeat business effects. A worked example shows a retry after a dropped response being detected as a duplicate, which is why a simple sent flag is insufficient for reconciliation.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in