Webhook Delivery Retry Policy: Undefined Default Retry Count

Webhook Delivery Retry Policy

When Harbor sends a webhook on an image push, the logs record a "Webhook failed, retrying" message. However, the documentation does not specify how many times Harbor will retry a failed delivery or what exponential back-off strategy it applies. This uncertainty can conceal a downstream failure where a webhook that never succeeds may be retried indefinitely, masking the root cause of a deployment failure in the target service.

Because the retry behavior is not documented, operators must infer the default from observed logs, which can vary between releases and between community and enterprise builds. The lack of a clear default also complicates troubleshooting when a webhook is configured to trigger on a specific event but never reaches the listener.

To diagnose such failures, the baseline retry logic and available overrides must be identified. The following questions highlight the gaps that remain unresolved:

• What is Harbor’s default retry count for webhook delivery when no explicit configuration is provided?
• Which back-off strategy (e.g., linear, exponential) does Harbor apply between retry attempts, and what are the interval parameters?
• How can an administrator explicitly set or override the retry count and back-off strategy in both community and enterprise Harbor deployments?