No dead letter queue for failed webhook deliveries

[ritaifeoluwa]

Description

The webhook delivery system has retry logic but no dead letter queue (DLQ). When a webhook delivery fails permanently (exhausts max attempts), the delivery record is marked as failed but the event data is lost. There is no way to replay failed deliveries.

Current behavior

Failed deliveries are marked with status='failed' and last_error. The payload is only stored in the delivery record and may be overwritten or cleaned up.

Expected behavior

• Store permanently failed deliveries in a DLQ (Redis sorted set or separate table)
• Include full payload, error history, and attempt details in DLQ entry
• Provide API endpoint to list DLQ entries
• Provide API endpoint to retry a DLQ entry (re-dispatch)
• Add TTL to DLQ entries for automatic cleanup

Suggested approach

Add a DLQ module that stores failed deliveries with full context. Add /webhooks/dlq GET and POST /webhooks/dlq/:id/retry endpoints. Use Redis sorted set with timestamp scores for efficient querying.

Labels

webhooks, api, feature

[devzakari-sketch]

Hi can i work on this task

[ayandipe]

@ayandipe has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer,
Kindly assign issue to me for precise and prompt resolution.
Regards

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayandipe to this issue.

[Toyosi5566]

@Toyosi5566 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I'd like to take this on; I'll implement the DLQ module using a Redis sorted set scored by timestamp for automated TTL management, preserve full event context on max retries, and wire up the inspection and replay endpoints with unit test coverage.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Toyosi5566 to this issue.

[drips-wave]

Congratulations, @Toyosi5566! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Toyosi5566: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊