Webhook Retry Policy
Talonic automatically retries failed webhook deliveries using exponential backoff. A delivery is considered failed if your server returns a non-2xx status or does not respond within 10 seconds.
Retry schedule
| Attempt | Delay | Cumulative time |
|---|---|---|
| 1 (initial) | Immediate | 0 seconds |
| 2 | 30 seconds | 30 seconds |
| 3 | 2 minutes | 2.5 minutes |
| 4 | 10 minutes | 12.5 minutes |
| 5 | 30 minutes | 42.5 minutes |
| 6 | 2 hours | 2 hours 42 min |
| 7 | 8 hours | 10 hours 42 min |
| 8 (final) | 24 hours | 34 hours 42 min |
Failure handling
After 8 failed attempts, the delivery is marked as permanently failed. Failed deliveries are visible in the Talonic platform under webhook logs. Each retry uses the same X-Talonic-Delivery-Id header, so implement idempotent processing.
Best practices
Return 200 OK immediately and process the payload asynchronously. Use the delivery ID for deduplication. Verify the HMAC-SHA256 signature on every attempt. Monitor delivery health in the platform dashboard.