Bitbucket webhooks randomly turn inactive

[Peter Suhm]

I'm the creator of a deployment tool called WP Pusher, that can install a WordPress theme or plugin from Bitbucket. During the installation, it will setup a webhook on Bitbucket in order to perform an update on every push.

However, some of my customers are reporting that webhooks randomly go into an inactive state on Bitbucket. WP Pusher doesn't touch the webhooks after they are created and this happens for webhooks they create manually again.

What could make a webhook go inactive, so that they need to manually re-activate it?

Any inputs are appreciated!

Thanks a lot!

[Phil Rittenhouse]

This just happened in one of our repos - did you get any response from Atlassian?

[Peter Suhm]

I did not. However, out best guess is that this happens because the webhooks time out too many times. For some reason, Bitbucket webhooks are only waiting for about 10 seconds I think. It seems that too many timeouts cause them to turn inactive.

[Phil Rittenhouse]

I found this bug report that confirms your theory

https://bitbucket.org/site/master/issues/14814/webhooks-bug-inactive

It's a "feature" that I, for one, would like to see removed