Delivery history
Inspect the relevant endpoint and delivery for HTTP status, errors and attempt count. A PDF can succeed while its webhook fails; these are separate outcomes.
Check the endpoint
Confirm the HTTPS URL and certificate, public reachability, raw-body signature verification, correctly decoded secret, timestamp handling and response latency.
Retry behavior
The current delivery flow allows up to 10 attempts with roughly 15-second intervals and small jitter after failed attempts. Queue/slot contention can extend overall duration, so this is not a fixed delivery-time guarantee. Receivers must handle duplicates without repeating business side effects.
Report a problem
Provide render/delivery IDs, time, HTTP status and a sanitized error. Do not include API keys, signing secrets or real customer payloads. Use a demo test event while diagnosing receiver behavior.