Retries, ordering and duplicates
Technical details of Empath's webhook retry schedule, rate limit, delivery order and duplicate handling, and how to design for them.
Technical details of how Empath retries, and what your receiver must handle.
How are failed deliveries retried?
- Attempts — Up to 4 in total
- Waits — about 1 minute, then 5 minutes, then 30 minutes
- Signing — Each attempt is signed again (new timestamp and signature); the
idstays the same - After the last attempt — The event isn't sent again. There's no manual retry in Empath.
- Rate limit — 100 deliveries a minute per webhook. Extra deliveries are delayed, not dropped.
Design for these
- At least once. The same event can arrive more than once (a retry after your receiver processed it but timed out). Store each
idand answer200to repeats without acting again. - No ordering guarantee. Deliveries run in parallel, so completed can arrive before assigned. Don't depend on order: e.g. if a completion arrives with no open ticket, log it anyway.
- Fast answers. Return 2xx quickly and queue the real work.
Still need help?
Reach out to your Partner Success Manager, or email us at support@empathmsp.com. We’re happy to help!
Related articles
- Request format: method, headers and timeouts
- How often an event can repeat
- Webhook health and the unhealthy alert