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

​
Common failures

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

Redbark disables the destination after 5 consecutive counted delivery failures, not after the first error. A delivery counts once after retries are exhausted or after a non-retried 4xx, except a Cloudflare challenge. A successful payload resets the counter. Fix the endpoint first, then use Re-enable from the destination row. Delivery resumes on the next sync. Timeouts, Cloudflare bot challenges, and outages of Redbark’s delivery service do not increment the counter, disable the destination, or stop the remaining batches. Any batch your endpoint has not confirmed 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.