October 28, 2022 . 1 MIN READ
Hanks for reaching out. Did I notice correctly that each of those webhooks set up on that repository is being triggered by the same exact events and making the same exact webhook deliveries to the same service? If so, then there are 20 webhooks doing the same exact thing — they’re delivering the same events 20 times to the same service. That kind of behavior is wasteful, and the webhook limits were introduced to prevent exactly that kind of wasteful behavior (which is a performance and reliability concern). We can’t support a higher number of webhooks for such a use-case.
Instead, the service you’re using should be able to work with just one webhook defined on the repository since the events they get from that webhook are the same as the events they get from 20 webhooks they have now. An alternative would be that you build a lightweight middleman proxy and point one webhook to that proxy. The proxy would then forward webhook deliveries it receives to any number of destination URLs that you want (since you control the proxy).
I wish I had better news for you, but I don’t. If you have any other questions — please let me know.
Reference:
https://github.com/microsoft/appcenter/issues/591
