Webhook Retry Policy

Here we provide an overview of how we attempt to retry sending webhook events.

In this guide we cover:

  • Why we attempt to retry
  • How the retry process works
  • Available interventions in the retry process

Why do we retry?

Marketplacer considers a successful webhook event to be one that generates a HTTP 2xx response back to Marketplacer. Webhook events are considered to be unsuccessful if:

  • The request timed out (currently 30s)
  • The request returns a non 2xx response code

In the case of a failure we enter into a retry process, we do this to give the webhook event the best chance possible of being successfully delivered.

The rest of this document details how we retry.

Retry Process

The retry process is shown below:

Retry Process

Some points to note about the retry process:

  • We use the “exponential backoff” pattern to retry:
    • The time interval between retries increases in an exponential way
    • Early retries are close together (e.g within seconds of each other)
    • Later retires are far apart (e.g. within hours or days of each other)
  • We retry 25x
  • The complete retry cycle (25 attempts) is expected to span ~20 days
  • The retry cycle can be cancelled
  • The retry cycle can be requeued (restarted)

Retry Interventions

In some circumstances you may be able to intervene in the webhook event / retry process, the ability to intervene is dependent on the “state” of the webhook event.

Possible states are described below:
  • Sent: The webhook has successfully been sent
  • Cancelled: The retry process has been stopped (by someone)
  • Failed: The retry process has ended unsuccessfully
  • “No Status”: The retry process is probably on-going…

An example of the interventions you can perform for each state are shown below:

Retry Process