monitoring
Retry
Automatically retry failed webhook deliveries with configurable backoff strategies.
How It Works
When a webhook delivery fails, HookSense automatically retries it with exponential backoff. The retry worker runs every minute and processes up to 10 jobs per cycle.
Backoff Schedule
| Attempt | Delay |
|---|---|
| 1 | 1 second |
| 2 | 5 seconds |
| 3 | 30 seconds |
| 4 | 5 minutes |
| 5 | 30 minutes |
After 5 failed attempts, the retry job is marked as exhausted.
Retry History
View all retry attempts from the Retries tab on your endpoint page. Each entry shows:
- Status: pending, running, succeeded, failed, exhausted
- Attempt count (e.g., "Attempt 3/5")
- Response status and duration
- Error messages
- Next retry time (for pending jobs)
- Auto-diagnosis with actionable suggestions
How Retries Are Triggered
You can manually create a retry job for any failed request from the endpoint page. The retry worker then handles scheduling and execution automatically.
Requires Sense plan. Uses Redis distributed locks for multi-instance safety.