Skip to main content

Webhook Delivery Issues

Use this page when a webhook did not arrive, kept retrying, or stopped after exhausting the current retry schedule.

Check These First​

  1. Confirm the job was created with delivery_mode=webhook.
  2. Confirm the target URL is public HTTPS and does not resolve to a blocked private or localhost address.
  3. Confirm your receiver returns a 2xx response after it accepts the event.
  4. Confirm you are verifying the signature against the raw request body.

Common Causes​

No Webhook Was Sent​

  • the job is still queued or processing
  • the create request was not in webhook mode
  • the webhook target was invalid at create time
  • polling the job or redeeming the download does not emit a new terminal event

Delivery Keeps Retrying​

  • the receiver returned non-2xx
  • the receiver timed out
  • the receiver failed TLS or connection setup
  • the signature check failed and the receiver rejected the request

Delivery Became Exhausted​

  • all retry attempts failed
  • the final export job state is still terminal, but Doqlo stopped retrying
  • webhook delivery outcome does not change billing or job-completion semantics

What To Do Next​

  • poll the job by job_id to confirm whether the export itself succeeded
  • if the job failed its threshold, read the failed payload or error.details; there is no download artifact to redeem
  • fix the receiver issue
  • submit a new job if you need a new terminal notification