What is the failed payload retention time?

When a webhook delivery fails (e.g., your server returns a 5xx status code, times out, or encounters a network issue), Blockferry buffers the payload and attempts automatic retries using an exponential backoff strategy. If all automatic retries are exhausted, the event is marked as Failed and moved to your Dead Letter Queue (DLQ).

Retention Window by Tier

• **Developer Tier:** Failed payloads are kept in the DLQ for **14 days**.
• **Scale Tier:** Failed payloads are kept for **30 days**.
• **Enterprise Tier:** Failed payloads are kept for **30 days** by default, with custom extension options up to **90 days** available.

Why Retention Matters

Having a reliable retention window allows you to:

1. Investigate Logs: Inspect the exact request payload sent, response headers returned, and error logs generated by your server.

2. Fix Backend Bugs: Deploy code fixes to your API without losing any data that was emitted during the downtime.

3. Trigger Manual Replays: Resend individual failed payloads or trigger bulk replays directly from the dashboard or the Blockferry CLI once your endpoints are healthy.