GitHub Community
How can I efficiently handle GitHub webhook retries and avoid duplicate event processing? #175725
-
Select Topic AreaQuestion BodyHello everyone, I’m building an integration that uses GitHub webhooks to trigger actions in my application. However, I’ve noticed that GitHub sometimes retries webhook deliveries if my server doesn’t respond quickly enough or returns errors. This causes duplicate events on my side, and I’m trying to find the best way to handle these retries gracefully. What are some common strategies or best practices to detect and ignore duplicate webhook events? Also, how can I ensure my webhook endpoint responds correctly to GitHub to minimize unnecessary retries? Any advice or example implementations would be really helpful! |
Beta Was this translation helpful? Give feedback.
Answered by
tranquillite-007
Oct 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working with GitHub webhooks, it’s totally normal to encounter retries because GitHub will resend events if it doesn’t receive a successful response from your server within a certain timeframe. To handle duplicate events gracefully, the most common approach is to use the unique X-GitHub-Delivery header that GitHub includes with every webhook payload. By storing these delivery IDs in your database or cache, you can check incoming requests against them and ignore any duplicates that you’ve already processed. This way, even if GitHub retries sending the same event, your system won’t act on it twice. Additionally, make sure your webhook endpoint responds quickly with a 200 OK status as s…