Delivery and Retry Logic

Tonder’s webhook system is designed for reliability. If your endpoint is temporarily unavailable, we will automatically retry the delivery.

​

How Webhook Delivery Works

The webhook delivery follows these sequential steps from event creation to final resolution:

​

Retry Policy and Configuration

When a webhook delivery fails, Tonder automatically retries according to a predefined policy:

​

Success and Failure Criteria

A delivery is considered successful if your endpoint responds with a 2xx HTTP status code within 30 seconds. Any other response is considered a failure, and a retry will be scheduled.

​

Common Failure Scenarios

Based on the original webhook system, these are the failure scenarios that trigger retries:

• 4xx errors (400, 401, 404, etc.) - Client errors indicating request problems.
• 5xx errors (500, 502, 503, etc.) - Server errors indicating endpoint issues.
• Timeouts when no response is received after 30 seconds.

After 3 failed attempts, the message is moved to a Dead Letter Queue (DLQ) for manual inspection.

​

Dead Letter Queue (DLQ)

The Dead Letter Queue stores failed webhook events that couldn’t be delivered after all retry attempts:

• Failed events are stored for manual inspection and potential reprocessing.
• Access is available through the Tonder dashboard or support team.
• Events can be manually retried after fixing endpoint issues.

​

Implementation Considerations

Key practices mentioned in the original webhook documentation:

• Acknowledge receipt immediately with a 200 OK status to prevent timeouts.
• Use the event_id to deduplicate events and prevent processing the same event twice.
• Keep detailed logs of all incoming webhook events for debugging purposes.
• Ensure that malformed payloads or processing errors don’t crash your system.

​

Next Steps

After understanding delivery and retry logic:

• Review webhook best practices for optimal implementation patterns.
• Troubleshoot webhook issues using the setup and management guide.
• Check out HTTP response codes for proper error handling and debugging.