Fix failed webhook deliveries

Open the webhook sync and select Deliveries. The latest attempt shows the response code, duration, and error returned by your endpoint.

Common failures

Result	What to check
401 or 403	Confirm your endpoint’s authentication and Redbark signature verification.
404	Check the configured path and deployment route.
429	Reduce endpoint rate limiting or accept batch requests. Redbark retries rate-limit responses.
5xx	Check the endpoint’s application logs. Redbark retries server errors.
Timeout	Return a 2xx response within 30 seconds. Acknowledge first and process larger batches asynchronously.
DNS or connection error	Use a publicly reachable HTTPS hostname. Private IPs, private DNS, IP literals, and internal-only Tailscale hostnames cannot receive deliveries.

Redbark splits large syncs into requests of up to 500 records. Your endpoint should validate and acknowledge the request quickly, then move expensive processing to a queue or background job.

Re-enable the destination

A non-timeout delivery failure disables the destination after retries are exhausted, or immediately for a non-retried 4xx. Fix the endpoint first, then use Re-enable from the destination row. Delivery resumes on the next sync. A timeout does not disable the destination or stop the remaining batches. Any batch your endpoint has not confirmed, whether it failed or timed out, marks the sync run as failed. The run’s counts include only confirmed batches; unconfirmed records are sent again on the next run. Deduplicate deliveries before processing them. If your endpoint returned success but failed to save the payload, use Replay webhook data.

Guide

Help center

Features

Destinations

Compliance

Fix failed webhook deliveries

Common failures

Re-enable the destination

​Common failures

​Re-enable the destination

Common failures

Re-enable the destination