Fallback mechanism

Our system maintains availability for HTTP endpoints and manages server maintenance and network variations. We monitor each Webhook endpoint's status by tracking message traffic. When we detect no activity from the publishing product, we actively send a Heartbeat service message at set intervals. This Heartbeat lets us check and ensure the endpoint's availability.
Webhook endpoints can have one of 3 statuses:
  • HEALTHY
    – everything working as expected
  • UNHEALTHY
    – unable able to deliver some of the messages
  • DISABLED
    – endpoint is temporarily switched off
When a webhook endpoint is DISABLED, it won't receive any messages. To turn on manually, use the self-service portal.
An endpoint switches from the
HEALTHY
to the
UNHEALTHY
state automatically. The system marks an endpoint as
UNHEALTHY
if the message delivery fails. Following the successful delivery of 5 consecutive messages, the system restores the endpoint's status to
HEALTHY
.
Webhook endpoint
image of webhook endpoint graph