Events & Attempts

What's an event?

A webhook event represents a webhook received from one of your sources. Events are used to keep track of all the webhooks received and their state.

webhook event

  • Status: The event status (pending, failed, successful, or on hold)
  • Event Date: The date the event was received
  • Attempts: The count of attempt that has been made
  • Webhook Connection: The webhook connection the webhook event is associated with
  • Next Attempt At: Automatically scheduled date for the next retry (attempt)

If you have multiple webhook connections for a source, Hookdeck will create as many events as there are connections.

Event Request

Each event also has an associated Event Request that contains the Headers, Path, Query and Body of the webhook request.

  • Headers: Every header from the event request (we do not include Hookdeck's headers). Headers is a JSON document
  • Path: The complete path of your event request.
  • Query: All the queries included in the URL of your event request.
  • Body: The event's payload. Can be a simple primitive (boolean, string, number, null) or JSON

event request

Event Request views

There are two ways you can inspect events.

  • Select the event directly in the dashboard to inspect from the right sidebar.
  • Select the View Event or the open icon from event request to open a page dedicated to the event request.

view-request

What's an attempt?

For each Event, an initial attempt is made to deliver the request to your Destination. If the request is successful, the retry strategy is disabled and your event will only have a single attempt.

Alternatively, new attempts will be made over time according to your retry strategy. Any given event can have up to 50 attempts. Each attempt can be browsed within the Event List by clicking an event or by going directly to the event page.

  • Status: The attempt status (pending, failed, successful, or on hold)
  • Attempt Date: The date the attempt was made
  • Attempt Number: The number of the attempt (nth position) for the associated event

Each attempt also has an associated Attempt Response that contains the HTTP Status and Body of the server response.

Attempts example

Error codes

If your destination was unreachable or failed to respond you will see the ERR code. A more specific error code can be found by clicking on the event.

The possible codes are:

  • CONNECTION_REFUSED: The request to your destination could not be made because the connection was refused.
  • CONNECTION_RESET: The request to your destination could not be made because the connection was forcibly closed by your server.
  • NOT_FOUND: The request to your destination could not be made because the domain or host was not found or unavailable.
  • TIMEOUT: The request to your destination exceeded the 30 seconds timeout. The request might have still been processed by your destination.
  • SELF_SIGNED_CERT: The destination's SSL certificate is self-signed (not supported by Hookdeck, the destination must have a valid certificate).
  • ERR_TLS_CERT_ALTNAME_INVALID: The destination's SSL certificate is not valid.
  • UNKNOWN: A uncategorized error occurred. If one of these errors is triggered, the technical team is notified and will investigate the situation.