Fix a slow webhook receiver
A receiver that does its work before it answers can be too slow for Jaah. Its deliveries still end Delivered, but only after several tries, so events reach your system late and some arrive twice. This guide finds a slow receiver in the delivery log and checks the fix. For deliveries that never arrive at all, see Fix a failing webhook.
You need to be an Owner or Admin of your organization, on a plan that includes webhooks.
- Open Settings, select Integrations, then Webhooks, and select the endpoint's name.
- Select the Deliveries tab. On a wide window, each row shows the receiver's Latency on the last try, in milliseconds, and how many Tries the delivery took. On a phone these two columns are hidden.
- Read the Delivered rows. A healthy receiver answers in well under a second, on the first try. A Tries count above 1 means the earlier tries failed, and a Latency of several thousand milliseconds means the receiver is close to the limit.
- Hover a Retrying status. Could not reach the endpoint within 10 seconds means your receiver took longer than Jaah waits, or refused the connection; the line also says when the next try is due.
- Change your receiver so it checks the signature, stores the event and answers with a
2xxstatus at once, then does the slow work, such as calling your tracker, afterwards. Have it skip a delivery it has already handled, since a retried event can arrive twice; see Answer and retries. - Back on the endpoint, select Send test. The Deliveries tab opens, and the
pingrow shows its Latency once your receiver answers. - Watch the next real deliveries: each should show Delivered with Tries at 1 and a low Latency. For any event still marked Retrying, select Redeliver to send it again at once.
A slow receiver also delays the endpoint's other events. Speeding the receiver up fixes both.
Related
- Receive events with webhooks: verify the signature and read the delivery log.
- How webhooks work: how a delivery moves from Queued to Delivered or Failed.
- Check whether an event reached your receiver: find one event's delivery and send it again.