Skip to main content

Webhook Retry

Webhook Retry lets you view failed webhook deliveries and retry them manually.

Accessing Failed Webhooks

Go to Settings → Logs & Monitoring and open the Webhook retries tab. (The old standalone Settings → Webhooks page has been folded in here and now redirects to Logs.) The tab displays a list of all failed webhook jobs with the following details:

  • Job ID -- Unique identifier for the webhook job
  • URL -- The target endpoint and HTTP method
  • Error -- The reason the delivery failed
  • Attempts -- How many times the system tried to deliver the webhook
  • Failed At -- When the last attempt failed

Retrying a Failed Webhook

Click the Retry button on any failed job to re-queue it for delivery. The system will attempt to send the webhook again using the same payload and configuration.

After a successful retry the job will be removed from the failed list.

Delivery pacing

To avoid overwhelming a destination, outbound webhooks are paced per destination host (independently for each workspace): deliveries to the same host are spread out to stay under a configured per-second rate, and one workspace's volume never throttles another's. When a host is momentarily over the rate, those deliveries are briefly delayed and then sent - nothing is dropped, and a delay does not count as a failed attempt. Separately, a host that keeps failing is short-circuited by a circuit breaker until it recovers.

Set your own per-host rates in Settings → Webhook delivery (requests/sec per destination host). Each rate is capped by a platform ceiling your operator sets, and a global default applies to any host you don't override. Most endpoints never need tuning.

Pagination

If there are many failed jobs the list is paginated. Use the Previous and Next buttons to navigate between pages.

Tips

  • Investigate the error message before retrying -- if the target endpoint is down the retry will fail again.
  • Check your webhook URL, authentication headers, and firewall rules when debugging persistent failures.
  • The system automatically retries failed webhooks several times before marking them as failed.