My webhook is turned off
On this page
When a webhook's deliveries fail many times in a row, OnBio turns it off and lets you know by email and in the panel. Find here what you see in its deliveries and follow the steps of that cause.
The destination does not answer
- How to recognise it
Deliveries appear as Undelivered with the reason The 8 attempts ran out and have no response from the destination. It usually happens when the server receiving the webhook is down or under maintenance.
- Where to check it
You see it in Integrations, in the webhook's detail. Each delivery shows its status, its attempts and its reason there.
- What to do
- 1. Fix the destination so it answers again.
- 2. Click Turn back on on the webhook.
- 3. Click Resend the undelivered deliveries.
The destination rejects the deliveries
- How to recognise it
The destination answers with an error instead of accepting the delivery. It happens if the address changed, if the destination demands another authentication or if it rejects the signature because it has an old secret.
- Where to check it
Open a delivery in the webhook's detail and read the Response from the destination.
- What to do
- 1. Correct the address with Edit, or put the current secret in the destination.
- 2. Click Send test event and check that it arrives as Delivered.
- 3. Click Turn back on and then Resend the undelivered deliveries.
The address points to a private network
- How to recognise it
Deliveries appear with the reason The destination points to a private network. OnBio only sends to public addresses on the internet.
- Where to check it
You see it in Integrations, in the webhook's deliveries. Filter by Undelivered to find them sooner.
- What to do
Change the address to a public one with Edit and turn the webhook back on. If the destination is on your network, publish it on the internet with https:// first.
Frequently asked questions
Do I lose the events while the webhook is turned off?
No. Deliveries stay as Undelivered and you recover them with Resend the undelivered deliveries. Each one goes out with its original event identifier so the destination recognises the ones it already had.
Was this helpful?
Need to talk to us?
If you didn't find what you were looking for, write to us. We reply within two working days.