How to Retry Failed Webhooks
Last updated: November 27, 2025
If a webhook to your endpoint fails (for example with a 404, 500, timeout, or any other delivery error), you can retry it directly from the Ivy Dashboard or programmatically via the API.
Where to See Failed Webhooks
All webhook deliveries are listed under your Webhook Subscription.
Each event shows:
Status: Pending, Delivered, Failed
Event type:
fx.initiated,fx.succeeded,fx.failed, etc.Delivery attempts with response details (HTTP status, payload, and error message)
Failed deliveries are clearly marked with a tag like “Has failed event”.
Clicking on an event opens the details view, where you can inspect:
The request payload Ivy sent
The response from your endpoint
The error message, e.g.:
Token "…" not found(404)
Retrying a Failed Webhook (Dashboard)
You can manually resend a failed webhook at any time:
Open the Webhook Subscription in your dashboard.
Select the event that failed.
In the right-hand details panel, click “Resend”.
This immediately re-delivers the exact same webhook payload to your endpoint.
The event will then appear with a new delivery attempt and an updated status.
Retrying All Webhooks via API
If you prefer to automate this or want to replay multiple events at once, you can use the API to retrigger deliveries.
Typical use cases include:
Recovering after an outage
Re-syncing state
Bulk-replaying all failed webhook attempts
Testing webhook handlers in development environments
Use the Webhooks API to resend individual events or retrigger all events for a subscription.
What Happens After a Retry
If the delivery succeeds → the event will move to Delivered.
If it fails again → it remains in Pending until the next automatic or manual retry.
Ivy will continue retrying according to the retry schedule unless the endpoint consistently returns errors.