Retries and pausing

Retries

A delivery fails when your endpoint answers outside 200–299, redirects, or doesn't answer within the timeout. JustDocs then tries again on a schedule. Each retry waits longer than the last:

Attempt	Waits	After the event
1	—	At once
2	1 min	1 min
3	5 min	6 min
4	30 min	36 min
5	2 h	2 h 36 min
6	6 h	8 h 36 min
7	12 h	20 h 36 min

Each attempt waits up to 10 seconds for an answer. An endpoint pauses after 20 failed attempts in a row.

After the last attempt, the delivery is marked failed and isn't tried again. The attempts cover about 20 hours, so an endpoint that's down for an evening catches up without losing events.

Every attempt has the same event id and JustDocs-Event-Id, and a new t in its signature.

Pausing

If an endpoint fails many attempts in a row, across all its events, JustDocs pauses it:

• Its waiting deliveries are marked failed, and new events aren't queued for it.
• The person who added it gets an email, or the team's owner if that person is no longer an owner or admin. It names the endpoint and the last problem.
• The endpoint shows Paused on the Webhooks page.

Fix the endpoint, then choose Resume. Deliveries start again with the next event. Events from while it was paused aren't re-sent. To catch up, list signing requests and fetch what changed.

A success at any point resets the count of failures.

Seeing what happened

Deliveries on each endpoint lists the latest deliveries: the event, its status (pending, delivered or failed), how many attempts it took, and the last status code or error. For example:

Error	Meaning
HTTP 500	Your endpoint answered with an error.
Redirected (HTTP 301); redirects aren't followed	Give the final URL instead.
timed out after 10 seconds	Answer sooner, and do the work afterwards.
refused: … resolves to a private address	The URL must resolve to a public address.