Skip to content

Notification log

The notification log records every attempt to deliver a webhook notification.

It provides visibility into how notifications were delivered, whether delivery succeeded, and what happened if delivery failed. Each delivery attempt is recorded independently and cannot be modified.

This allows integrators to verify that external systems received events and to diagnose delivery problems.

What is logged

A log entry is created for every delivery attempt of a webhook notification.

This includes:

  • the webhook that attempted delivery
  • the event that triggered the notification
  • the target endpoint
  • the delivery timestamp
  • the delivery result

If delivery fails and the system retries the request, each retry attempt is recorded as a separate log entry.

All attempts related to the same event reference the same webhook, event, and payload.

Field reference

Typical fields stored in the notification log include:

  • Webhook name – the webhook configuration that produced the delivery
  • Event name – the notification event that triggered the webhook
  • Target URL – the endpoint receiving the webhook request
  • Delivery timestamp – when the delivery attempt occurred
  • Delivery status – the outcome of the attempt
  • HTTP response code – the status returned by the receiving system
  • Attempt number – which retry attempt this represents
  • Payload hash – identifier of the delivered payload
  • Response body – response returned by the receiving system (if present)
  • Error message – description of delivery errors when they occur

These fields allow delivery attempts to be inspected and compared across retries.

Statuses

Each delivery attempt is recorded with one of the following statuses:

  • Delivered
    The receiving system responded with HTTP 200, indicating the notification was accepted.

  • Failed
    The receiving system returned a non‑200 response or a network error occurred.

  • Retrying
    A previous delivery attempt failed and another retry has been scheduled.

These states make it possible to understand whether a notification has been successfully delivered or is still being retried.

Retention

Notification log entries are immutable records of delivery attempts.

They allow inspection of:

  • the original delivery attempt
  • the cause of failures
  • subsequent retry attempts
  • the final delivery outcome

Because retries create new log entries, the full history of delivery attempts remains visible for troubleshooting and auditing.

Related concepts