Webhook delivery failure during high-volume repository events

Bitbucket Cloud Webhook Reliability

Integrating Bitbucket Cloud with external monitoring tools requires reliable event delivery via webhooks. When a destination endpoint returns a non-2xx HTTP response code, the system logs the delivery failure. However, there is uncertainty regarding the consistency of automatic retry logic across different event types during periods of high repository activity.

The goal is to ensure critical alerts are received without introducing excessive notification noise or losing event data due to transient endpoint timeouts.

• Component: Webhook Delivery System
• Constraint: Non-2xx HTTP response handling

Does Bitbucket Cloud implement a standardized retry policy for all webhook event types after a delivery failure? If retries occur, what is the specific backoff interval or maximum attempt limit before the event is dropped?