As per Retry policy:

If a webhook is sent to its callback URL but fails, Jira Cloud will attempt to resend it up to five times. Each subsequent attempt is delayed with a randomized exponential back-off algorithm. The first retry occurs after at least 10 seconds, and the last between 15 and 30 minutes from the first failure.

Sometimes webhooks may take a while to complete, either due to poor network connections, or due to long processing times on the remote application, we should allow configurable timeouts to help end users work around this issue.

Why This Is Important

It's important to reduce the amount of retry messages in the external system

Workaround

Use X-Atlassian-Webhook-Retry in header to identify retry requests and skip them.