ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Process Ghost CMS webhook events (member.added, subscription.created, etc.) exactly once in a downstream system despite Ghost's built-in retry mechanism, which re-sends the same payload up to 10 times over ~24 hours when the receiver returns a non-2xx response or times out. Constraints and uncertainty Ghost v5.x does not include a unique event identifie
Ghost CMS & Knex.js: Handling Retries Without Duplicate Writes The goal is to ensure that a transient failure during a Ghost write operation does not create duplicate content when retried. Ghost relies on Knex.js transaction rollback and unique slug indexes, turning a repeated insert into a 409 Conflict instead of a duplicate row. An open design decision
Goal: Verify whether the Azure Service Bus duplicate‑detection cache persists after a namespace restart, queue pause, or scale operation so that applications can predict if a retried message with the same ID will be silently dropped or treated as a new message. Uncertainty: Public documentation does not state if the cache is cleared during pause, scaling, or
ghost