Retry Policy

Successful delivery

A webhook delivery is considered successful when your server responds with a 2xx status code (e.g. 200, 201, 204).

Timeout

A webhook will timeout after 25 seconds of waiting for a response. If the timeout is reached, it is counted as a failed delivery.

Tip

Process webhook payloads asynchronously and respond with 200 immediately. This prevents timeouts when your processing logic takes time.

Failed deliveries

A delivery is considered failed when:

• Your server responds with a non-2xx status code (e.g. 400, 500)
• The connection fails entirely (e.g. DNS resolution failure, connection refused)
• The request times out (no response within 25 seconds)

Retry schedule

Failed webhooks are retried with a short delay:

Attempt	Delay
1st retry	5–30 minutes after initial failure
2nd retry	5–30 minutes after 1st retry
3rd retry	5–30 minutes after 2nd retry

A webhook will be retried up to 3 times.

Automatic disabling

If a webhook fails more than 3 times (including the initial attempt), it will be automatically disabled. Once disabled, no further events will be sent to that endpoint.

A disabled webhook must be manually re-enabled through the Mobiledock Integration Hub or by contacting Mobiledock support.

Failure logging

The response content and status code of the last failed delivery attempt are recorded. If you configured failure notification emails on your webhook, those addresses will receive a notification when the webhook is disabled.

Best practices

• Respond quickly — return 200 before processing the payload
• Implement idempotency — the same event may be delivered more than once during retries
• Monitor your endpoint — set up failure notification emails to catch issues early
• Keep your endpoint available — ensure your server has high uptime to avoid automatic disabling