Retry Logic and Webhook Logs

Retry Logic

Webhook requests may encounter failure due to network or destination server issues. In such cases, Alloy employs an automatic retry mechanism. Initially, retries are scheduled at intervals of 1 second, 1 minute, and 10 minutes after the initial failure. Subsequently, retries continue on an exponential backoff for a duration of 24 hours from the time of the first failure.

It's important to note that new webhook events take priority over retrying failed events. Consequently, during peak traffic hours, the retry schedule may experience delays.

What if webhooks are failing?

If your webhooks fail to deliver 100 times continuously in a 72 hour period, it will be disabled automatically. You can re-enable it by setting to active in your webhook settings.

Webhook Logs

You can view a real-time log of all webhook attempts, both successful and failed, in the settings section of your Alloy dashboard.

Each log shows the following details

1. Time - The timestamp Alloy made the request to the client's webhook server
2. Name - The name set when creating the webhook
3. Event - Webhook event type that triggered the webhook request
4. Attempt - The number of retries Alloy has attempted. You can click into each specific retry in it's own log
5. Endpoint - Webhook URL the request was sent to
6. Response - HTTP Response Code returned when making the request
7. Exception (if applicable) - Error message if something goes wrong
8. Payload Content - Click on a specific log to see more details, including all previous attempts for a webhook

See this help article for more information on Alloy's webhook logs.