When your webhook fails, RunLater automatically retries with exponential backoff. Here's how to configure it.
How Retries Work
- First attempt fails
- Wait
retry_delayseconds - Wait
retry_delay × 2seconds - Wait
retry_delay × 4seconds - Continue until max retries reached
Configuration Options
| Setting | Default | Range |
|---|---|---|
| Retry Count | 3 | 0-10 |
| Retry Delay | 60s | 1-3600s |
| Timeout | 30s | 1-300s |
What Triggers a Retry?
- HTTP 5xx errors (server errors)
- Connection timeouts
- Network failures
- DNS resolution failures
What Doesn't Retry?
- HTTP 4xx errors (client errors) – your request needs fixing
- HTTP 2xx (success) – it worked!
- HTTP 3xx (redirects) – followed automatically
Example Retry Timeline
With retry_count: 3 and retry_delay: 60:
| Attempt | Time | Wait Before |
|---|---|---|
| 1 | 0:00 | - |
| 2 | 0:01 | 60s |
| 3 | 0:03 | 120s |
| 4 | 0:07 | 240s |
Best Practices
- Use higher retry counts for critical webhooks
- Increase timeout for slow endpoints
- Check logs to understand failure patterns
- Don't retry on 4xx – fix the request instead