Skip to main content

Retry Behavior

Use this page when you need to understand how Doqlo treats failed webhook deliveries.

Current Retry Schedule​

If a delivery attempt fails, Doqlo currently retries at these offsets from the first failed attempt:

  • +1 minute
  • +5 minutes
  • +30 minutes
  • +1 hour
  • +2 hours

After the final failed attempt, the delivery becomes exhausted.

What Counts As A Failure​

Doqlo treats these conditions as failed delivery attempts:

  • a non-2xx HTTP response
  • a timeout while waiting for the receiver
  • a connection or TLS failure
  • a target that becomes invalid at delivery time

Receiver Best Practices​

  • return a 2xx response quickly
  • verify the signature before doing expensive work
  • process events idempotently by event_id
  • move slower downstream work to your own queue after the 2xx

Important Notes​

  • Doqlo webhook delivery is bounded, not indefinite.
  • Exhausted webhook delivery does not rewrite the final export job state.
  • Retry behavior is separate from billing and does not create a new quota charge.
  • Polling and download redemption do not trigger new webhook deliveries.