Webhook deliveries are failing
A delivery counts only when your endpoint answers with a 2xx status in time. Recent activity shows the status or the response for each failure.
Owner
Ovante counts a delivery as sent only when your endpoint answers with a 2xx status before Ovante's timeout. A redirect counts as a failure, because Ovante never follows one, and so does an address that points to a private network. Each request carries an X-Ovante-Signature header; if your code rejects it, that's a failure too. After many failures in a row, Ovante turns the connection off and it shows Disabled.
Fix it
- 1Open Settings → Integrations and the card you connected: Custom webhook, Zapier or Make.
- 2On the connection's menu, click Recent activity. Each failure shows the status code, a timeout, or the start of your endpoint's response.
- 3Fix the endpoint: answer quickly with a 2xx, use the final URL with no redirect, and check signatures with the secret from View signing secret. After Roll signing secret, update your code.
- 4Click Send test.
- 5If the connection says Disabled, click Resume on its menu.
Not this?
- Nothing arrives for a request: requests send nothing until you approve them. See Review requests.
- Salesforce stopped syncing: see Salesforce says Reconnect.
Was this helpful?
Related
Send events to a webhookOvante posts a signed JSON message to your HTTPS endpoint each time an event you picked happens, retries what fails, and logs every delivery.PayloadsEvery webhook is one JSON envelope with the event's id, type and time, and a data object shaped for its kind: a ticket, an order, a gift or a contact.Use Zapier or MakeZapier and Make connections are webhooks with their own cards. They send the same events and payloads, need no signature check, and turn off when the hook is deleted.