Browse the docs

Retries and limits

If your server is down for a while, you do not lose events. EzReach keeps trying, slowly, for about a day.

What counts as success

Your server answers 2xx within 10 seconds. Anything else is a failure: another status (a 3xx too, redirects are never followed), no answer in time, a refused connection or a TLS problem. EzReach does not keep what your server answers.

Retries

After a failure EzReach waits and tries again. 7 tries in all, over about 20.6 hours. Then it gives up on that event.

TryWaits before it
1Sent as soon as the event happens
21 minute
35 minutes
430 minutes
52 hours
66 hours
712 hours
  • A retry sends the same body and the same event id, signed again with a new time. Use the id to ignore an event you have already handled.
  • Events can arrive out of order and, rarely, twice. Do not rely on the order. Use the times inside data.
  • In Settings > Developers > Webhooks you see the log of deliveries for 30 days, with the status code and the reason of each failure. Choose Resend to try an event again at once.
  • Send test event is never retried and never counts towards turning an endpoint off.

When an endpoint is turned off

If every try to an endpoint fails for 3 days in a row, EzReach turns the endpoint off. Events waiting for it are given up, and the owners of your workspace get an email that names the endpoint's host. The panel shows "Turned off automatically" with the date. Fix your server, then turn the endpoint on again. The 3-day clock starts afresh.

An endpoint you turn off yourself also gives up its waiting events. Nothing that happened while it was off is sent afterwards.

Busy endpoints

If an endpoint has 10,000 events waiting, EzReach stops recording new email.opened and email.clicked events for it until it catches up. Every other event is always recorded. To avoid this, answer fast and do the work later, or subscribe only to the events you use.

Erased people

When a contact is erased in EzReach, the stored events about them are emptied (only their ids stay) and the ones still waiting are not sent. "Resend" refuses them.

Limits

WhatLimit
Endpoints per workspace (a turned-off endpoint counts until you delete it)5
Address of an endpoint2,048 characters
Description of an endpoint200 characters
Time your server has to answer10 seconds
Size of one request body64 KB
Tries for one event7 over about 20.6 hours
The log of deliveries is kept30 days
The previous secret still signs after a rotation24 hours
Events waiting for one endpoint before opens and clicks are dropped10,000
A request is refused as too old when its time is more than5 minutes from your clock