← Back to Docs

Retry Strategies

When your webhook fails, RunLater automatically retries with exponential backoff. Here's how to configure it.

How Retries Work

  1. First attempt fails
  2. Wait retry_delay seconds
  3. Wait retry_delay × 2 seconds
  4. Wait retry_delay × 4 seconds
  5. Continue until max retries reached

Configuration Options

SettingDefaultRange
Retry Count30-10
Retry Delay60s1-3600s
Timeout30s1-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:

AttemptTimeWait Before
10:00-
20:0160s
30:03120s
40:07240s

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