Bitbucket webhooks randomly turn inactive

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!

1 answer

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

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.

I found this bug report that confirms your theory


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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

296 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you