Repository navigation
docs(backend): define webhook safe recovery and retry semantics (SSB-… - #1429
Merged
github-actions[bot] merged 1 commit intoOct 25, 2026
Conversation
|
@cleank0de is attempting to deploy a commit to the ritik4ever's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document and formalize safe recovery, retry, and dead-letter rollback semantics for the Webhook delivery workflow (duplicate delivery after timeout and temporary 5xx responses).
Project Area:
backendBatch ID:
SSB-2026-152Key Invariants & Semantics
500,502,503,504), the worker retains the active delivery row inpendingstatus and schedules a retry using configured backoff intervals (5s,15s,60s,300s,900s). Every retry re-sends the identicalIdempotency-Key(stellar-stream-<delivery id>) header and exact canonical JSON body so endpoints can safely deduplicate received requests.max_attemptswithout a2xxresponse, the delivery is removed fromwebhook_deliveriesand moved towebhook_dead_lettersin a single transaction. No duplicate entries or dangling delivery rows remain.Changes
docs/webhook-monitoring.mdwith explicit safe recovery and rollback semantics forSSB-2026-152.Closes #1095