Description of the bug
It seems like after connecting a webhook listener, if the url ever returns a non 200, or times out, the webhooks just stop firing off. This makes it rather challenging to build around, as execution could stop without an obvious signal.
1 Like
Yes, unfortunately webhooks aren’t exactly meant for public consumption at the moment, so as you’ve noticed, they get immediately disabled when the response they receive from the remote is not a 2xx.
We will add your +1 to expand Webhook functionality so it is more robust.
2 Likes