Retries & Dead Letter Queue
Forge guarantees at-least-once delivery. We assume your endpoint might be down temporarily, and we have robust mechanisms to ensure you eventually get your data.
Retry Policy
If your server returns any HTTP status code >= 300, or if the request times out (10s), Forge considers delivery failed. We then schedule retries with exponential backoff.
| Attempt | Delay | Total Wait Time |
|---|---|---|
| 1 (Initial) | 0s | 0s |
| 2 | 30s | 30s |
| 3 | 5m | 5m 30s |
| 4 | 30m | 35m 30s |
| 5 (Final) | 6h | ~6.5h |
Dead Letter Queue (DLQ)
If the final retry attempt fails, the event is moved to the Dead Letter Queue. It allows you to inspect payload data and manually replay it once your fix is deployed.
Tip: DLQ events are retained for 7 days (Start/Standard) or 30 days (Plus/Max).
Manual Replay
You can replay events from the Dashboard. A replayed event retains its original event_id andoccurred_at timestamp, but will have a new signature timestamp.