Replays and Retries

​

Replays

Occasionally, a change or issue in your internal environment may cause webhook deliveries to fail. Replays help you address scenarios like:

• Service Downtime: If your service was down and missed events.

• Endpoint Misconfiguration: If you had the wrong endpoint configured.

​

Replaying a Single Event

If you want to replay a single event, you can find the message from the console and click the options menu next to any of the attempts. From there, click “Resend” to send the same message to your endpoint again.

​

Bulk Recovery

If you need to recover from a service outage and replay all events since a given time, you can do so from the Endpoint page:

1. Go to the endpoint’s details page.

2. Click Options > Recover Failed Messages.

3. Choose the broader time window from which you want to recover.

For more granular recovery—for example, if you know the exact timestamp you want to recover from—you can click the options menu on any message from the endpoint page, then click “Replay…” and choose “Replay all failed messages since this time.”

​

Retry Policy

When Straddle attempts to deliver a webhook and fails to get a successful response (2xx status code), it will keep trying to deliver the same event using an exponential backoff schedule. This gives you time to fix the issue without losing any events.

Retry Schedule:

Automatic retry stops after any of these conditions are met:

• A 2xx response is received.

• All 8 attempts have been completed.

• The endpoint is disabled.

If all attempts fail for 5 consecutive days, the endpoint is automatically disabled.

​

Disabled Endpoints

If your webhook endpoint does not respond with a 2xx status code consistently, it will be automatically disabled after 5 consecutive days of failures. The timer starts after the first failure, and a single successful delivery resets the timer.

You will receive an email notification when the webhook is disabled. You can re-enable a disabled webhook in the dashboard by editing the webhook.