Why there is a feature that disables webhook after a failed response?

Our product team modeled our webhooks approach based on the approach of some leading fintech providers. For instance, Stripe takes a very similar approach to retries and disabling in case of errors (Use incoming webhooks to get real-time updates ). Our goal is to help customers manage errors on their side by providing multiple retries and notifications while balancing appropriately handling failing requests. We suggest that as a best practice for using our webhooks, you first send back a 200 response and then run any processing logic that may take longer (Webhooks (Real-Time Events) ). You are also able to immediately reactivate any webhook that has been deactivated after all retries failed directly through the interface by going to General Settings> Developers > DigiFi Webhooks.