Does GitHub automatically disable webhooks if the request is not valid (HTTP Status 410) in the third-party system?

[narendran-kannan]

Select Topic Area

Question

Body

I'm currently working on a project that heavily relies on GitHub webhooks. I'm trying to understand the behavior of GitHub when it comes to webhook failures.

Specifically, I would like to know:

Does GitHub automatically disable a webhook if there are continuous failures? If so, after how many consecutive failures does this occur?
If the endpoint server returns a 410 Gone status, does GitHub disable the webhook immediately? (Similar to Azure DevOps Service Hooks)
Is there any way to configure these behaviors?
Any insights or references to official documentation would be greatly appreciated.

Thank you in advance for your help!

[gm3dmo]

Does GitHub automatically disable a webhook if there are continuous failures? If so, after how many consecutive failures does this occur?

No. GitHub will not disable the webhook. GitHub expects that you resolve issues happening on the third party endpoint for the webhook.

Is there any way to configure these behaviors?

The behaviour of a webhook is not configurable in this way.

Guidance for our webhooks can be found at:

https://docs.github.com/en/webhooks

You can create a test to see a response using Flask, here I asked Copilot to "create python program using flask that responds only with 410 gone on POST to /webhook":

from flask import Flask, Response

app = Flask(__name__)

@app.route('/webhook', methods=['POST'])
def gone():
    return Response("410 Gone", status=410)

if __name__ == '__main__':
     app.config['DEBUG'] = True
     app.run(host='0.0.0.0', port=8080)