Retries and deliveries
What happens when your endpoint fails, and how to see and resend deliveries.
Retries
A delivery fails when your endpoint doesn't answer with a 2xx within 10 seconds (redirects aren't followed). Cueston tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours: six attempts in all. Then the delivery is marked failed.
An endpoint whose deliveries have all failed for 3 days is turned off, and the people who can change workspace settings get an email. Fix it, send a test event, then turn it back on. Turning an endpoint back on clears its failure streak; turning it off stops queued retries.
Delivery log
Each endpoint keeps its deliveries for 30 days: the event and payload, the status, the number of attempts, the last response code or error, how long it took, and up to 4 KB of your response body.
- See them in Settings → Integrations → Webhooks, or with
GET /api/webhooks/{id}/deliveries(filter bystatusandeventType). - Redeliver one with
POST /api/webhooks/{id}/deliveries/{deliveryId}/redeliver. It's the same event, with the sameidand payload and a fresh signature, sent once.
Testing
Send test event (or POST /api/webhooks/{id}/test) sends a signed webhook.test event right away and shows the result. It works on a turned-off endpoint too, so you can check a fix before turning it back on.
During development, any HTTPS tunnel to your machine works as an endpoint URL.