Skip to main content

​
Retry or replay

A retry never sends the event again to a destination that already got it. Use retry after an outage. Use replay to test a new destination with an old event. Each retry or replay uses one credit for each event. You can do up to 60 retries and replays a minute.

​
Batch retry

The Needs retry view on the Events page lists events whose latest attempt to an active destination is dead. This includes an event that reached some destinations but not all.
  1. Open Events and click the Needs retry chip. Or open the link in a failure alert email.
  2. Add filters if you need them: destination, time range, source or a search.
  3. Tick events (up to 100), or click Retry all to retry every event that matches.
Owners and admins can do batch retries. With a destination filter, hooksnode retries that destination only. An event leaves the view when its retry is queued. It comes back only if that retry is also dead.
The filters are in the page URL. Share the link and your teammate sees the same list.

​
Retry from the API

The API answers 409 when no delivery of the event is dead, and 402 when you have no credits. See the API reference.

​
Buffered events

On a Pro project, an event that arrives when no active destination takes its source is buffered. hooksnode stores it and charges one credit, but sends it nowhere. The sender gets:
To send a buffered event, add a destination, open the event and click Play. hooksnode sends it to the destinations that are active now and take that source. Buffered events are deleted after 30 days. On the Free plan, a project with no destination refuses events with 400.